Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: "Mark Aufflick" <mark at aufflick dot com>
Subject: SUCCESS: Partial success compiling Sybperl 2.18 under cygwin
Date: Jan 10 2006 5:56AM

Excellent - thanks for that. The CONFIG file is well documented - not
sure why I didn't figure that out myself ... always looking for the
hard way!

So after I:

* disable DBLib as below
* perl Makefile.PL
* amend the Makefiles as per the email linked below
* make

The build process goes fine. It seems that and are also
skipped - I assume they depend on the old DBLib?

The test process isn't smart about skipping tests that need DBLib, or - according to the test harness, t/5_sybperl.t
failed 200% of it's tests!!

all the _ct_ tests passed however which is excellent!

Thanks again.


PS: Leaving entire annoying email chain below for best googling usefulness

On 1/1/1970, ""

>I don't remember right now how I did the .a files, and I don't have access
>to the computer that might have the information at the moment (I'm at work,
>the computer's at home :-)
>However, if you edit the CONFIG file in the sybperl source directory and
>set DBLIBVS to 0 then the Sybase::DBlib build should normally be skipped,
>and all should be well. There may be test errors (I haven't made sure that
>make test does the right thing in this situation in a long time), but at
>least you shouldn't get any build errors.
> - 09/01/2006 06:21
>Sent by:
>To:    sybperl-l
>Subject:    Fwd: Partial success compiling Sybperl 2.18 under cygwin
>Hello everyone.
>I have hit the problem (documented in numerous places) that current
>versions of the Sybase open client for Windows don't seem to contain
>enough symbol information to build cygwin .a files from their dll's.
>In order to work around that, Michael Peppler "built a set of .a files
>(libcs.a, libct.a and libblk.a) that provide these entry points" - see
>According to this email, these archives were built to allow DBD::Sybase
>to be compiled against new open client dlls under cygwin. I followed the
>steps in that email (including modifying all Makefiles in the
>Sybase::Sybperl distro), plus I copyied the sybase ocs header files to
>I have been able to get it all to compile except for the DBLib directory.
>I assume that's because Michael has only supplied .a files for CS, CT
>and BLK.
>I get a whole bunch of linker errors like:
>DBlib.o:DBlib.c:(.text+0x2214): undefined reference to `_dbgetuserdata@4'
>DBlib.o:DBlib.c:(.text+0x2c2f): undefined reference to `_dbconvert@28'
>etc. A quick google for dbgetuserdata tells me that it is indeed a Sybase
>DBLib api call.
>I'm not sure how Michael built these files (from memory of other emails
>i have seen it was from an older version of OCS?), but I guess I have
>two options:
>1/ somehow generate an appropriate symbol file for dblib
>2/ remove the dblib stuff from the Sybperl module since I don't think
>any of my code needs it.
>Does anyone have any info that would be useful for me?
>sybperl version: 2.18 (from
>perl version: 5.8.7
>cygwin version: not sure, but it's less than 2 months old
>ocs version: 12.5.1
> Mark.)
>This message and any attachments (the "message") is
>intended solely for the addressees and is confidential.
>If you receive this message in error, please delete it and
>immediately notify the sender. Any use not in accord with
>its purpose, any dissemination or disclosure, either whole
>or partial, is prohibited except formal approval. The internet
>can not guarantee the integrity of this message.
>BNP PARIBAS (and its subsidiaries) shall (will) not
>therefore be liable for the message if modified.
>                ---------------------------------------------
>Ce message et toutes les pieces jointes (ci-apres le
>"message") sont etablis a l'intention exclusive de ses
>destinataires et sont confidentiels. Si vous recevez ce
>message par erreur, merci de le detruire et d'en avertir
>immediatement l'expediteur. Toute utilisation de ce
>message non conforme a sa destination, toute diffusion
>ou toute publication, totale ou partielle, est interdite, sauf
>autorisation expresse. L'internet ne permettant pas
>d'assurer l'integrite de ce message, BNP PARIBAS (et ses
>filiales) decline(nt) toute responsabilite au titre de ce
>message, dans l'hypothese ou il aurait ete modifie.
> iBurst Wireless Broadband from $34.95/month
> Forward undetected SPAM to: