This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygwin dlls needed to run binutils

On 24/11/2011 7:07 AM, Dave Korn wrote:
On 23/11/2011 16:59, Ryan Johnson wrote:
On 23/11/2011 11:47 AM, Surrounder wrote:
Larry Hall (Cygwin) wrote:
A cygcheck on 'ld' shows cyggcc_s-1.dll is pulled in as a result of a
dependency on cygintl-8.dll.  I don't see a dependency on cygz.dll but
perhaps another tool from the package pulls that one in.
I found out that the needed dllÂs depend on the .\configure I do, is
there a
way to find out what options were used makeing binutils last time out
of the
I tried searching a list where I can maybe find info about what cygwin
is used for what function in binutils.
I suspect that --disable-nls would remove the dependency on libintl, but
I don't know what would pull in libz.
   That'll probably be the support for zip-compressed debug info sections that
was added to the mainline sources around this time last year.  It can be
disabled by passing "--with-zlib=no" to configure, or apparently also as a
side-effect of "--disable-nls" (according to a quick reading of the configure
scripts, I haven't tested.)
That's weird... why does NLS have anything to do with zip-compressed debug info? Or do they both use zlib and somebody just forgot to update the configure script?


-- Problem reports: FAQ: Documentation: Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]