ld --auto-import for cygwin and libtool
Sun Jul 22 01:37:00 GMT 2001
Any idea when this might make it into the official Cygwin binutils ? even as
a experimental test version.?
I'm sure many cygwin porters would find this very very useful, instead of
having to use ugly hacks. Especially since an earlier Cygin binutils version
used to support it
----- Original Message -----
From: "Robert Collins" <email@example.com>
> I've cc'd this for wide exposure.
> I'm looking for any tests that folk would like to see on Paul
> Sokolvsky's auto-import PE hack in order to consider it for inclusion in
> binutils. Libtool could benefit from this patch, as it would allow fully
> automatic dll building on cygwin, _but_ the patch should be widely
> available for that to be worth considering.
> Paul a while back made a rather neat hack to pe to allow automatic
> importing of symbols without needing decoration. This allows libraries
> to be built with out any decoration in the headers - ie in standard UNIX
> format. AFAIK the patch has languished due to no one reviewing it.
> So... I've spent some time putting it through it's paces, and it seems
> to work without any issues at all. There were some teething issue, due
> to the patch not being developed for Cygwin, but for pw32. Thats been
> resolved (see below).
> I'm very happy with the way the patch performs, it builds all the
> existing decorated code I could find without trouble, and quite happily
> builds fully non-decorated code. Ralf Habacker has built KDE 1 with it,
> with a modified libtool.
> I've uploaded to my homepage a modified libtool 1.4 that uses
> gcc -shared and Paul's auto-import ld. This libtool passes all tests
> including tests that fail with the current production cygwin code except
> 1) build-relink.test spits out
> "shlibpath_overrides_runpath should be set to yes."
> I'm not sure what that should be for cygwin, so I'm referring the
> question to the libtool list :]. I'm happy to dig further if the issue
> is a bug, but if setting this to yes is the correct action there's
> little to do :].
> 2) quote.test - which I have discussed in the copied email below.
> My homepage can currently be found at
> I've also uploaded a binutils src tarball with the modified ld. I've
> modified it a little further to avoid some cygwin dll symbols it was
> picking up by mistake. A patch for that against a recent binutils is
> there as well. My patch also differs from Paul's original in that I've
> left disabled the auto-image-base option, which can cause issues with
> cygwin, due to a issue previously discussed. That option isn't part of
> the auto-import logic and thus shouldn't be part of this discussion IMO.
> (And should not be enabled by default!).
> I may well have broken libtool stuff, and there are things that can be
> tidied a bit, but this should work for anyone with the modified ld. Also
> the ld indenting is probably naffed, but it should be good enough for
> review by anyone interested.
> I'm not subscribed to binutils, but am to libtool - if you just reply to
> binutils I'll miss your reply.
> ----- Original Message -----
> From: "Robert Collins" <firstname.lastname@example.org>
> To: "Gary V.Vaughan" <email@example.com>
> Sent: Monday, June 11, 2001 9:19 PM
> Subject: libtool that passes all tests
> > I'm down to depdemo-nofast with no failures. I think that by the time
> > go to bed tonight I'll likely have a nearly-no-failures cygwin libtool
> > here. Are you interested in a tarball of such a thing (with a copy of
> > Paul's ld ?)
> > (the failures are: quote.test is failing, "error on mkdir .libs" but I
> > think thats because cygwin returns an error when you mkdir an existing
> > directory - does unix return an error for that? build-relink.test is
> > also failing, and thats my current target. )
> > I ask whether you want that in preference to a patch, because with the
> > MLB merge, I imagine that any patch will be outdated before I can
> > Also I don't know if I've broken any other things or not :].
> > I have one change that definately isn't a proper solution - and thats
> > the extra_LIBS thing I asked about on the list a few days ago. The
> > needs to go in the search path, or the test script needs to add the
> > libs/extra dir to the normal path when the test is run on cygwin, for
> > proper solution.
> > Of course, the ld needs proper peer review, but I figured that a fully
> > functional libtool would be a good starting point for saying "well it
> > seems to work" :]
> > Rob
More information about the Cygwin-apps