[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cygwin build problem with m4 HEAD

From: Eric Blake
Subject: Re: cygwin build problem with m4 HEAD
Date: Fri, 09 Sep 2005 06:06:12 -0600
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

Hash: SHA1

According to Ralf Wildenhues on 9/9/2005 1:31 AM:
>>>I notice that it is attempting to link against /usr/lib/libltdl.dll.a,
>>>which comes from libtool 1.5.18, rather than /usr/local/lib/libltdl.dll.a,
>>>which is my installed libtool 2.1a, and I am pretty sure that
>>>lt_dlhandle_fi{nd,rst} were added in 2.x, explaining the link failure.
>>>What I can't track down is why the link command is looking in the wrong
>>>directory, and thus getting the wrong symbols for libltdl.
>>I managed to work around the earlier bug report by configuring m4 using 
>>included-ltdl, but it still feels hackish.  I wish I knew why m4 was trying 
>>link against the wrong libltdl.  In the meantime, once I was using my 
>>workaround, it exposed another bug.
> I'm sorry for not having looked into this yet; it may be related to
> another possible bug I am seeing.  Can you post the value of $(LIBLTDL)?

On a fresh m4 ./configure, without --with-included-ltdl, @LIBLTDL@ is
replaced with -lltdl, @LTDLINCL@ with -I${top_srcdir}/ltdl, @INCLTDL@ with
- -I${top_srcdir}/ltdl, and HAVE_LTDL is set to 1.

On a fresh m4 ./configure --with-included-ltdl, @LIBLTDL@ is replaced with
${top_builddir}/ltdl/libltdlc.la, LTDLINCL and INCLTDL are unchanged, and
HAVE_LTDL is no longer defined.

make install for libtool reported
- ----------------------------------------------------------------------
Libraries have been installed in:

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-LLIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
- ----------------------------------------------------------------------

I have not defined LD_RUN_PATH, /usr/local/bin but not /usr/local/lib was
in my PATH.  Was there something I was missing when configuring m4 on
telling it where the full path where to look for the installed libtool
libraries?  And does libtool really want /usr/local/lib on the PATH, or
does it look in /usr/local/bin/../lib automatically if /usr/local/bin is
on the path?  Could it be a bug in libtoolize for not setting up
./configure to know where the matching installed libltdl is in relation to
the installed libtoolize?

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


reply via email to

[Prev in Thread] Current Thread [Next in Thread]