[avail for test] readline-4.2-1
Thu Jun 7 15:27:00 GMT 2001
----- Original Message -----
From: "Charles Wilson" <email@example.com>
> Robert Collins wrote:
> The ONLY reason I'm concerned about bash as an exception to that rule,
> is because Chet maintains BOTH bash AND readline. Because he cares, I
I'm on the fence on this one. The breakage is caused not because they
have the package in a subdir (they do provide --with-included-readline)
but because their header is picked up by default and then linked against
the system readline. Thats a build bug yes.
> <snip comparison of default behaviors>
<SNIP static vs dynamic first-in logic>
I see your point about libtool aligning with the system. Do remember
that pw32 and mingw are also affected by our changes with respect to
> > I don't think that is an issue:
> > a) Present day: all the libtool created libraries are
> > cyglibfoo-version.dll. And they don't provide an ordinal .def file,
> > all linked apps will be by name.
> > b) The libraries you are shipping are linked to by name if you use
> > default headers, no? So again, that shouldn't be an issue.
> I *think* so. There was a problem around libpng-1.0.9/1.0.11 where
> missing functions changed the autoassigned ordinals...and stuff broke.
> I created a .def file to maintain the <old> ordinal numbers -- but the
> .def does not specify NONAME, so the names should be exported.
<snip quoting> >
> > Basically, ordinals are a optimisation, and the dll _creator_
> > whether linking to ordinals is allowed. No .def file, and/or no
> > (they are optional) and it cannot happen.
> What happens when you strip a dll? (All dlls are shipped stripped by
> default). nm -a on a stripped dll shows "no symbols" -- but
> indicates that the symbol export table is still there. However,
> actually linking with the import lib, which is (of course) not
> and so contains all of the symbol names.
So there's no issue :}. The dll's export table is used by the win32
runtime linker, and the import lib by ld.
> > 'Course, testing is probably needed, or a quick mail to the binutils
> > list/search the binutils archives.
> testing. The problem is, I really don't know how to look at a given
> executable, say foo.exe, which depends on bar.dll and baz.dll, and
> Ah, yes, foo is linked by name to bar.dll, but its linked by ordinal
> to baz.dll.
> So, how can you test anything if you don't know how to 'evaluate' the
make a dll foo, with 3 exports -
make a client program and link to foo.
now rebuild the dll with
the client program, without relinking should still work. If it doesn't,
it was linked by ordinal.
There is a much harder issue to solve I ran into last night, so I'm now
putting time into evaluating Paul Solovosky's ld that auto-imports, and
no longer needs any decoration. (The problem to solve is building static
libs from the same source via libtool when the static|shared compile
needs extra user defines. Urgh)
If that looks good, I'll see what I can do to get a libtool that
supports its tested and running. (Hopefully with a little guidance :] )
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin