--- Begin Message ---
Send Libtool mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
http://mail.gnu.org/mailman/listinfo/libtool
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Libtool digest..."
Today's Topics:
1. Re: libtool 1.5.x linking regression on Tru64 (-pthread)
(Albert Chin)
2. Get cheap via-gra (Kyle Barrera)
3. Re: libtool: link: warning: '[.la file]' seems to be moved
(Albert Chin)
4. libtool 1.4.3 searches /usr/lib before -L<dir> (Pieter Grimmerink)
5. Re: libtool 1.4.3 searches /usr/lib before -L<dir> (Tim Mooney)
6. libtool-1.5.2 searches /usr/lib before -L<dir> (Pieter Grimmerink)
7. Re: libtool-1.5.2 searches /usr/lib before -L<dir>
(Kevin P. Fleming)
8. Re: libtool-1.5.2 searches /usr/lib before -L<dir>
(Pieter Grimmerink)
9. Re: libtool-1.5.2 searches /usr/lib before -L<dir>
(Pieter Grimmerink)
10. Re: libtool-1.5.2 searches /usr/lib before -L<dir> (Russ Allbery)
11. Re: libtool-1.5.2 searches /usr/lib before -L<dir> (Albert Chin)
----------------------------------------------------------------------
Message: 1
Date: Thu, 19 Feb 2004 19:27:25 -0600
From: Albert Chin <[EMAIL PROTECTED]>
Subject: Re: libtool 1.5.x linking regression on Tru64 (-pthread)
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Thu, Feb 19, 2004 at 12:07:21PM -0600, Tim Mooney wrote:
> Given a project that uses libtool 1.4.3 and also uses pthreads, it's
> common to have `-pthread' in CFLAGS when configuring the project. The man
> page for cc defines -pthread as:
>
> -pthread
> Directs the linker to use the threadsafe version of any library speci-
> fied with the -l option when linking programs. This option also tells
> the linker to include the POSIX 1003.1c-conformant DECthreads inter-
> faces in libpthread when linking the program. This option also defines
> the _REENTRANT macro.
>
> In any case, for 1.4.3 compiling with libtool works correctly, and linking
> shared libraries also works as expected.
>
> If the project is updated to use libtool 1.5.2, though, linking fails,
> because `-pthread' is now being passed to ld, and ld doesn't understand
> that option.
>
> I haven't had a chance to look much at the problem, but thought I would
> report it. Please let me know if I can provide additional information.
I noticed this too but haven't had a chance to look into it. Maybe
this weekend.
--
albert chin ([EMAIL PROTECTED])
------------------------------
Message: 2
Date: Fri, 20 Feb 2004 09:13:06 -0600
From: "Kyle Barrera" <[EMAIL PROTECTED]>
Subject: Get cheap via-gra
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL: http://mail.gnu.org/pipermail/libtool/attachments/20040220/9fc17c88/attachment.htm
------------------------------
Message: 3
Date: Fri, 20 Feb 2004 12:51:26 -0600
From: Albert Chin <[EMAIL PROTECTED]>
Subject: Re: libtool: link: warning: '[.la file]' seems to be moved
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Fri, Feb 13, 2004 at 02:07:12PM -0600, Albert Chin wrote:
> ltmain.in prints out a warning when it thinks the .la file isn't in
> $libdir:
> if test "$absdir" != "$libdir"; then
> $echo "$modename: warning: \`$deplib' seems to be moved" 1>&2
> fi
>
> However, if $absdir has "..", and it resolves to $libdir taking ".."
> into consideration, the warning is still printed. How do we solve
> this? (cd $absdir; /bin/pwd) won't work because of automounter
> madness.
>
> Or should we just remove the message?
Anyone?
--
albert chin ([EMAIL PROTECTED])
------------------------------
Message: 4
Date: Fri, 20 Feb 2004 22:00:47 +0100
From: "Pieter Grimmerink" <[EMAIL PROTECTED]>
Subject: libtool 1.4.3 searches /usr/lib before -L<dir>
To: "Libtool" <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
I've asked for help about this problem twice in the last
few weeks, without any replies.
In the meantime I've done some searching in the libtool
list history, and I came across this:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg04324.html
This seems to be exactly the same problem I'm having.
Now I'm wondering, has the reason, and possibly a
solution for this problem been found in the meantime?
Regards,
Pieter
------------------------------
Message: 5
Date: Fri, 20 Feb 2004 16:29:22 -0600 (CST)
From: Tim Mooney <[EMAIL PROTECTED]>
Subject: Re: libtool 1.4.3 searches /usr/lib before -L<dir>
To: [EMAIL PROTECTED]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: TEXT/PLAIN; charset=US-ASCII
In regard to: libtool 1.4.3 searches /usr/lib before -L<dir>, Pieter...:
>I've asked for help about this problem twice in the last
>few weeks, without any replies.
I saw your posts, but don't recall whether this is something you've
tried with libtool 1.5.2 or not. Have you? The libtool developers
have expressed extreme reluctance to spend much time on code that is
an evolutionary dead end. All new work is going into the 1.5.x and
later lines of development.
>In the meantime I've done some searching in the libtool
>list history, and I came across this:
>
>http://www.mail-archive.com/[EMAIL PROTECTED]/msg04324.html
If you download libtool 1.4.3 and look at ltmain.in, you'll see about
a dozen places where
newlib_search_path
is set to something. In each case, the assignment ends up looking like
newlib_search_path="$newlib_search_path <something else here>"
If you try systematically changing these to
newlib_search_path="<something else here> $newlib_search_path"
you should eventually be able to arrive at the combination of settings
that are causing the problem for you. My *guess* (and that's all it is)
is that it's either the place where it's under a "case" for `-L', or it's
the place where you have
newlib_search_path="$newlib_search_path $ladir"
Do some testing, and report back what you find. Better yet, test with
libtool 1.5.2.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
------------------------------
Message: 6
Date: Sat, 21 Feb 2004 02:07:43 +0100
From: Pieter Grimmerink <[EMAIL PROTECTED]>
Subject: libtool-1.5.2 searches /usr/lib before -L<dir>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I've downloaded and installed libtool-1.5.2, and tried the same as with my
reports about 1.4.3
It behaves exactly the same, it finds libraries in /usr/lib, instead of where
-L wants them to be found.
Then I replaced
newlib_search_path="<something else here> $newlib_search_path"
by
newlib_search_path="$newlib_search_path <something else here>"
everywhere in ltmain.in, one by one, but that did not make a difference.
Then I took another look at the --debug output of the libtool script, and it
occurred to me that libtool is actually looking for an .la script.
When it does not find the .la script, it passes the original -lxyz parameter
to gcc, instead of trying to replace it by the library it thinks should be
used.
gcc knows how to use -L<dir>, and links against the correct library.
So I removed the .la script belonging to my library in /usr/lib, libtool does
not find it anymore, and now it works.
But I guess that's not the preferred way to handle this...
Regards,
Pieter
------------------------------
Message: 7
Date: Fri, 20 Feb 2004 18:24:39 -0700
From: "Kevin P. Fleming" <[EMAIL PROTECTED]>
Subject: Re: libtool-1.5.2 searches /usr/lib before -L<dir>
Cc: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Pieter Grimmerink wrote:
> So I removed the .la script belonging to my library in /usr/lib, libtool does
> not find it anymore, and now it works.
Are you saying there was a .la file in /usr/lib for a library that is
_not_ in /usr/lib? Or are there multiple versions of this library on the
system, one in /usr/lib and one elsewhere?
------------------------------
Message: 8
Date: Sat, 21 Feb 2004 11:31:09 +0100
From: Pieter Grimmerink <[EMAIL PROTECTED]>
Subject: Re: libtool-1.5.2 searches /usr/lib before -L<dir>
To: "Kevin P. Fleming" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
On Saturday 21 February 2004 02:24, Kevin P. Fleming wrote:
> Pieter Grimmerink wrote:
> > So I removed the .la script belonging to my library in /usr/lib, libtool
> > does not find it anymore, and now it works.
>
> Are you saying there was a .la file in /usr/lib for a library that is
> _not_ in /usr/lib? Or are there multiple versions of this library on the
> system, one in /usr/lib and one elsewhere?
There are multiple versions of this library, one in /usr/lib (with a .la
file), and one elsewhere, without a .la file.
I need the one elsewhere, because I'm crosscompiling.
I know I should probably try what happens when both have a .la file, but the
second one was not built with libtool, it's a stripped down version for an
embedded target.
Regards,
Pieter
------------------------------
Message: 9
Date: Sat, 21 Feb 2004 18:23:56 +0100
From: Pieter Grimmerink <[EMAIL PROTECTED]>
Subject: Re: libtool-1.5.2 searches /usr/lib before -L<dir>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
On Saturday 21 February 2004 11:31, Pieter Grimmerink wrote:
> There are multiple versions of this library, one in /usr/lib (with a .la
> file), and one elsewhere, without a .la file.
> I need the one elsewhere, because I'm crosscompiling.
> I know I should probably try what happens when both have a .la file, but
> the second one was not built with libtool, it's a stripped down version for
> an embedded target.
OK, now I've given the library in -L<dir> a .la file as well.
Now both libraries have a .la file, and libtool-1.5.2 uses the correct
library, in -L<dir>. So that's solved then.
I don't want to go back to 1.4.3 to try whether that also would have worked
with both .la files in place.
Thanks for the help guys.
Regards,
Pieter
------------------------------
Message: 10
Date: Sat, 21 Feb 2004 10:43:22 -0800
From: Russ Allbery <[EMAIL PROTECTED]>
Subject: Re: libtool-1.5.2 searches /usr/lib before -L<dir>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Pieter Grimmerink <[EMAIL PROTECTED]> writes:
> OK, now I've given the library in -L<dir> a .la file as well. Now both
> libraries have a .la file, and libtool-1.5.2 uses the correct library,
> in -L<dir>. So that's solved then.
So, basically, it sounds like libtool has reinvented the very annoying
Tru64 library search mechanism, where any shared libraries are found
before static libraries regardless of the relative order on the library
path, except as applied to *.la files.
This sounds like a bug to me. The Tru64 behavior causes no end of
surprises and means that you can't easily link with (often newer) locally
installed static libraries if the operating system happens to come with
some dynamic library by the same name.
What was the reason for this change, or was it accidental?
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
------------------------------
Message: 11
Date: Sat, 21 Feb 2004 12:54:51 -0600
From: Albert Chin <[EMAIL PROTECTED]>
Subject: Re: libtool-1.5.2 searches /usr/lib before -L<dir>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Sat, Feb 21, 2004 at 10:43:22AM -0800, Russ Allbery wrote:
> Pieter Grimmerink <[EMAIL PROTECTED]> writes:
>
> > OK, now I've given the library in -L<dir> a .la file as well. Now both
> > libraries have a .la file, and libtool-1.5.2 uses the correct library,
> > in -L<dir>. So that's solved then.
>
> So, basically, it sounds like libtool has reinvented the very annoying
> Tru64 library search mechanism, where any shared libraries are found
> before static libraries regardless of the relative order on the library
> path, except as applied to *.la files.
I don't think libtool is doing this. It looks like it's preferring
libraries with corresponding .la files. Even that is a bug though.
Someone needs to dig further.
--
albert chin ([EMAIL PROTECTED])
------------------------------
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
End of Libtool Digest, Vol 15, Issue 11
***************************************
--- End Message ---
