> It's up to you -- that's why I coded the libtool changes so that your
> improvements could be a "drop in" fix. I think it'd be "nice" is file
> could tell me that a given file was an import lib or a (regular) lib,
> but it isn't necessary.
>
> There's certainly no rush.
I will see.
The problem i
Ralf Habacker wrote:
o speed problem with the internal "win32_libid()" routine is partially
fixed -- approx 35% speedup. Ralf Habacker is working on some
modifications to the official fileutils distribution (specifically,
file.exe) that should allow an additional 8% speedup without additional
chan
> o speed problem with the internal "win32_libid()" routine is partially
> fixed -- approx 35% speedup. Ralf Habacker is working on some
> modifications to the official fileutils distribution (specifically,
> file.exe) that should allow an additional 8% speedup without additional
> changes to lib
libtool-devel has been updated to the 20030216 CVS codebase, as well as
libltdl3. The 20030216 release has been in 'test' for a week, with no
ill effects -- save a known problem with wacky pseudo-cross-compiler
setups (see 'Open issue' below).
Note that libtool-devel-20030103 depends on autoco
4 matches
Mail list logo
