![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've been using an M4 macro (derived from the one in the sqsh source package) for some time now but the omission of the ".a" libraries in the 12.5.1 distribution (for Solaris at least) has broken it. Before I go hacking at it again, I'm curous if anyone else has something more "mainstream". Is there an accepted procedure for determining compile and link flags required to use the OCS libraries? |
#3
| |||
| |||
|
|
What information is missing when the .a files aren't available? |
|
IIRC the sqsh macro only looks at the .a file to find the OCS version, and from there determines whether to include the -ltli library in the link (OCS 10x needs this, OCS 11.x and later does not.) You could replace this version check with something like running isql -v and parsing that. |
#4
| |||
| |||
|
|
"Michael Peppler" <mpeppler (AT) peppler (DOT) org> wrote in message news an.2004.07.26.07.21.16.114460 (AT) peppler (DOT) org...The "Man" himself! I was considering dropping a note directly to you but opted for the newsgroup instead. Got the best of both. Cool What information is missing when the .a files aren't available? If I'm reading it correctly, the AC_SYBASE_ASE macro in the aclocal.m4 for sqsh-2.1 is looking for each .a (blk, cs, ct, comn, (syb)tcl, intl, and tds). For each it finds, it's adding "-lfoo" to SYBASE_LIBS. Mine does the same and find's nothing with 12.5.1 on Solaris. |
|
It's not right WRT portably detecting a MT environment or it's handling of the insck. Sybase added a version suffix to the library filename. It's wrong BTW; they used the release version (i.e. libinsck.so.12.5.1) rather than it's interface version. Dynamic linking will be hosed with 12.5.2+... (If you have the right contacts, pass them this; http://www.gnu.org/software/libtool/manual.html#SEC32) |
![]() |
| Thread Tools | |
| Display Modes | |
| |