-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zachary Pincus wrote:
| Thanks for your reply, Peter.
|
| I do agree that libtool is behaving correctly here. However, the fact
| remains that this "correct behavior" is causing problems with the motif
| libraries where libXm does indeed depend on libX
On Wed, Jan 28, 2004 at 10:59:32PM +0900, Peter O'Gorman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Zachary Pincus wrote:
> | Which libtool translates into the following link command:
> | g++ -dynamiclib -single_module -o OUTPUT.dylib [input .o files]
> | /usr/X11R6/lib/libX11.
Thanks for your reply, Peter.
I do agree that libtool is behaving correctly here. However, the fact
remains that this "correct behavior" is causing problems with the motif
libraries where libXm does indeed depend on libX11 and so forth, but
nevertheless, must be on the link line *before* the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zachary Pincus wrote:
| Which libtool translates into the following link command:
| g++ -dynamiclib -single_module -o OUTPUT.dylib [input .o files]
| /usr/X11R6/lib/libX11.dylib /usr/X11R6/lib/libXp.dylib
| /usr/X11R6/lib/libXext.dylib /usr/X11R6/lib/
Hello,
I've run across a linking problem with libtool that frankly has me
stymied. (I'm using version 1.5.2, on Mac OS X 10.3, if that matters.)
The general gist is that when libtool automatically decides what
libraries to link in, it can get the link order wrong, which causes
dependency pr
Alexandre Oliva wrote:
> One simple solution would have been to move -lpthread first in the
> list of dependencies of libjava.
I tried that. I'm not quite sure why it didn't work.
> I'm not sure we should introduce thread-awareness in libtool
I've often wished gcc handled the variety of system
On May 16, 2001, Bryce McKinlay <[EMAIL PROTECTED]> wrote:
> Jeff Sturm wrote:
>> On Sun, 13 May 2001, Bryce McKinlay wrote:
>> > libtool inserting lib flags ("-lgcc_s -lc -lgcc_s") into the gcj link
>> > command line _before_ other lib flags which we are passing to it. This
>> > means that libc
