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
per
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 p
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
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
binaries?
I tried searching a list where I can maybe find info about what cygwin dll
is used for what function in binutils.
Larry Hall (Cygw
On 11/23/2011 10:37 AM, Surrounder wrote:
I compiled binutils within cygwin 1.7.9-1 and was wondering why I not only
need the cygwin1.dll to run them under windows, I also need the cygz.dll and
the cyggcc_s-1.dll
Last time I compiled only cagwin1.dll was necessary. Anybody knows if I do
sth. wr
5 matches
Mail list logo