Gerrit P. Haase wrote:
Hallo Charles,
Am Samstag, 29. März 2003 um 06:47 schriebst du:
This means the cyggdbm_devel-3.dll is also in the libgdbm3 package.
^^^^^^ _compat
Oops. <g> I notice my original message also has a ton of grammatical and spelling errors, too...I'm so embarrassed.
Further, it means that any application code that USED the "dbm" or "ndbm" personalities, now needs to link with "-lgdbm_compat -lgdbm" and not just -lgdbm. Most programs don't use the compatibility personalities, and can simply continue to link only against -lgdbm.
I linked just with libgdbm_compat for the NDBM_File and ODBM_File Perl modules, works fine, all tests successful.
Woo-hoo! Thanks, Gerritt.
So, you didn't need to ALSO link those against -lgdbm? I mean, cyggdbm_compat-3.dll depends on cyggdbm-3.dll according to cygcheck. I thought that meant you had to include the dependencies on the link line **even** if your app doesn't directly access any of the stuff in the remote dependency?
e.g. chuck.exe uses cyggdbm_compat-3.dll
cyggdbm_compat-3.dll depends on cyggdbm-3.dll
chuck.exe does NOT directly use anything in cyggdbm-3.dllBut I still have to say
gcc -o chuck.exe ...... -lgdbm_compat -lgdbm
right? wrong?If I'm right, then I'm confused as to how Perl built properly -- unless perl uses libtool for linking (in which case intrinsic deps are handled by libtool automatically via the .la mechanism)
--Chuck
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
