>it seems, that it solves the problem.... Good to hear that.
> >Some questions: >1. Where should I add veo07.c? > - do you mean here? > file: ./sys/desc/sqlpyd.dld: > --------------------------------------- > ... > &endif > > &if $OSSPEC in [ OSF1 ] > ?linkoption : -expect_unresolved * > &endif > > vin77.c > vin28.c > veo07.c > &if $OS in [ WIN32, OS2 ] > splib > vos40-1.c > sqlusr-NoNI > &else > ... > --------------------------------------- Yes. If you don't get unresolved references when *importing* sapdb.sql, then it's OK. >2. Does the integration of sql03_init_multi_threaded > make problems when used with python which was compiled > without thread support? It requires some functions from the pthread library. When python is not linked with pthread support, it could be that the module sapdb.sql could not get imported because of this. I've heard that I could add libpthread to the linkstep for sqlpyd.dld, thus circumventing the problem. But I'd have to test that first. Or I'll just knock on wood (see point 4 later). >3. I downloaded the sources of Version 7.4.3.32 > I know that you made changes, especialle to the python >driver (vin77.c) > *after* 7.4.3.32 was released. > > a) are these changes in the downloadable sources? > > b) is it possible that you send me the lates version of your > vin77.c, vin28.c, ... (python driver specific files)? >[if a) is not true] Well, MySQL AB changed the license of the clients for a reason, so we're not longer allowed to release anything using the LGPL. >4. Will you add sql03_init_multi_threaded to the 7.6 sources? Probably. Python configure is setting the default to thread support anyway. Daniel Dittmar -- Daniel Dittmar SAP Labs Berlin [EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
