Hi,
Was I correct to file this bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55607
Or did we misinterpret the docs of -export-symbols?
Thanks,
Havoc
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
Martin Baulig <[EMAIL PROTECTED]> writes:
>
> somewhere between libtool 1.3.x and 1.4, you did the following:
>
>
> 1999-12-15 Thomas Tanner <[EMAIL PROTECTED]>
>
> * ltmain.in: don't remove multiple occurences from dependency_libs
> of a library, otherwise many depend
Hi,
I've been setting up the 4 packages glib, pango, atk, and gtk+ to
build as part of one giant tarball.
So this means I link each library against the libtool libs in the
builddir of the other libraries.
The problem here is getting our test and demo programs to run without
actually installing
Bernard Dautrevaux <[EMAIL PROTECTED]> writes:
> A necessary (and sufficient AFAICT) condition would be that, given the fact
> that libtool remember library dependencies, one use a tsort-like tool to
> topologically sort all the libraries, while detecting loops in the
> dependencies, and emitti
Eric Lemings <[EMAIL PROTECTED]> writes:
>
> Well I for one was unaware of the PKG_CONFIG_PATH variable. If that is true
> however, how are client packages supposed to know where their .pc files are
> supposed to be installed if this variable can be changed? Right now, I think most
> assume th
Alexandre Oliva <[EMAIL PROTECTED]> writes:
> On Apr 22, 2001, Havoc Pennington <[EMAIL PROTECTED]> wrote:
>
> > pkg-config has some intelligence, i.e. if you request two libs at once
> > it will nuke duplicate flags and order the -l flags properly.
>
> Err.
Alexandre Oliva <[EMAIL PROTECTED]> writes:
>
> You wouldn't. This is totally out of the scope of libtool. Libtool
> is about linking with libraries, not compiling source files so that
> they can be linked with them. Not that it couldn't be extended so as
> to record user-directed flags at th
[EMAIL PROTECTED] writes:
> Ick! If anything, pkg-config should use libtool. I don't think libtool
> should *depend* on pkg-config at all. Libtool might be enhanced to
> help pkg-config get at certain data but I hope it does no more than
> that. That said, *.la files are already easy to parse.
Alexandre Oliva <[EMAIL PROTECTED]> writes:
> On Apr 21, 2001, Eric Lemings <[EMAIL PROTECTED]> wrote:
>
> > 2.0 spawned a separate tool called pkg-config that allows all packages
> > to use one tool rather than several different scripts to query compile
> > flags, link flags, and other configur
Alexandre Oliva <[EMAIL PROTECTED]> writes:
> On Apr 21, 2001, Havoc Pennington <[EMAIL PROTECTED]> wrote:
>
> > This would also help handle -R on Solaris and stuff like that.
>
> If it could handle a list of packages at once, yes, it would probably
> help on o
Hi,
I'm all for it, but someone has to do the work. ;-)
This would also help handle -R on Solaris and stuff like that.
Havoc
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
11 matches
Mail list logo
