On Tue, Oct 03, 2006 at 09:14:37PM +0200, Kurt Roeckx wrote:
>
> Also, libtool has a problem with it, since it can reorder things.
> See http://bugs.debian.org/347650
Yeah, reordering of command-line args is not nice. I think Ralf has a
patch to fix this but it's post-2.0 work.
--
albert chin (
On Mon, Oct 02, 2006 at 05:26:43PM -0500, Albert Chin wrote:
> > Debian has a patch that sets link_all_deplibs to no. This basicly
> > doesn't use dependency_libs for shared linking. Note that this causes
> > various problems for which there are open bugs in the Debian bug
> > tracking system.
>
Albert Chin wrote:
> And how do you handle the inherited_linker_flags variable in .la files?
Dunno, but hopefully implementation details can be overcome (by guru's with
ample libtool-fu).
Either libtool needs to address the issues raised in this thread, or distros
will start/continue to simply o
On Tue, Oct 03, 2006 at 08:16:47AM -0500, Rex Dieter wrote:
> Albert Chin wrote:
>
> > I don't see how libtool can intelligently decide the minimum set of
> > libraries needed to satisfy the link.
>
> pkgconfig has both
> Libs =
> Libs.private =
> The latter being for private and/or static linki
Albert Chin wrote:
> And, even for .pc files, it doesn't mean you get _only_ the libraries
> you need. What if someone has "Requires: -lpng -lz" in a .pc file?
> Then you have a dependency on libpng and libz, which is unnecessary as
> libpng already depends on libz.
If the "Requires" is legit, wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Compilation of CVS m4 currently fails on cygwin when configured with
- --disable-static, due to global variables referenced in the library export
lists. If nothing else, this is yet another example of why global
variables in libraries are bad. Someho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have been trying to plug a memory leak in CVS m4:
$ m4 -m load
include(forloop.m4)dnl for a forloop macro to make the leak more obvious
forloop(i,1,5000,`unload(gnu)load(gnu)regexp(123,\(4\)?2)')
Part of the leak was libltdl's fault, and I sent a p
wgcc is a cross-compiler tool primarily written for Microsoft's Interix.
Its primary purpose is to produce native Windows binaries (internally
using the Microsoft Tool chain), and to mimic the behaviour of the GNU
compiler collection. This means that wgcc understands many of GCC's
command line argu
