[python-sybase] Build runs into problems with sybasect extension

John Craig john at alphagconsulting.com
Sun Feb 11 11:06:57 EST 2007


Hi Folks,

I'm sure this is just some kind of simple thing, but I am not an 
experienced gcc user and I am quite unsure how to proceed. I'm trying to 
build on Win XP. I've had to tell it to use the cygwin compiler and that 
works, to a point. I do not have the mxDateTime package mentioned in the 
"Prerequisites" section, but it appears that is not absolutely necessary 
(and since I don't need to manipulate datetime values at the moment, I 
was hoping it wouldn't matter).

Do I need the Sybase header files in some include directory (other than 
the one they're in under the Sybase install)? The SYBASE & SYBASE_OCS 
environment variables are properly set.

Any suggestions welcomed. Output of the compiler follows.

John


A bunch of stuff has been built successfully. Using this command:

setup.py build -c mingw32

But, when it gets to this point, I get pages of errors (similar ones are 
omitted and I've put in ... )--some the line-breaks have been changed 
for clarity:

building 'sybasect' extension
writing build\temp.win32-2.5\Release\sybasect.def
C:\cygwin\bin\gcc.exe -mno-cygwin -shared -s 
build\temp.win32-2.5\Release\blk.o
build\temp.win32-2.5\Release\databuf.o build\temp.win32-2.5\Release\cmd.o
 build\temp.win32-2.5\Release\conn.o build\temp.win32-2.5\Release\ctx.o 
build\temp.win32-2.5\Release\datafmt.o
 build\temp.win32-2.5\Release\iodesc.o build\temp.win32-2.5\Release\locale.o
 build\temp.win32-2.5\Release\msgs.o build\temp.win32-2.5\Release\numeric.o
 build\temp.win32-2.5\Release\money.o 
build\temp.win32-2.5\Release\datetime.o
 build\temp.win32-2.5\Release\sybasect.o 
build\temp.win32-2.5\Release\sybasect.def
 -LC:\SybaseClient125\OCS-12_5\lib -LC:\Python25\libs -LC:\Python25\PCBuild
 -llibblk -llibct -llibcs -lpython25 -lmsvcr71 -o 
build\lib.win32-2.5\sybasect.pyd
build\temp.win32-2.5\Release\blk.o:blk.c:(.text+0xa0): undefined 
reference to `_blk_bind'
build\temp.win32-2.5\Release\blk.o:blk.c:(.text+0x1da): undefined 
reference to `_blk_describe'
...
    There's dozens of errors that mention various _blk and _cs routines
...
build\temp.win32-2.5\Release\locale.o:locale.c:(.text+0x66): undefined 
reference to `_cs_loc_alloc'
build\temp.win32-2.5\Release\locale.o:locale.c:(.text+0x178): undefined 
reference to `_cs_loc_drop'
...
build\temp.win32-2.5\Release\numeric.o:numeric.c:(.text+0x78): undefined 
reference to `_cs_convert'
build\temp.win32-2.5\Release\numeric.o:numeric.c:(.text+0x15b): 
undefined reference to `_cs_convert'
...
build\temp.win32-2.5\Release\money.o:money.c:(.text+0x70): undefined 
reference to `_cs_convert'
build\temp.win32-2.5\Release\money.o:money.c:(.text+0x151): undefined 
reference to `_cs_convert'
...
build\temp.win32-2.5\Release\datetime.o:datetime.c:(.text+0x3a): 
undefined reference to `_cs_dt_crack'
build\temp.win32-2.5\Release\datetime.o:datetime.c:(.text+0x59): 
undefined reference to `_cs_dt_crack'
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1







More information about the Python-sybase mailing list