[ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.1.acd6540-1 (x86/x86_64)

Sun Apr 6 22:38:00 GMT 2014

On 2014年04月06日 17:11, m0viefreak wrote:
> The latest mingw64-binutils is broken for me:
>> $ echo 'main() { }' > a.c; /bin/x86_64-w64-mingw32-gcc a.c
> /usr/bin/x86_64-w64-mingw32-ld: cannot find default-manifest.o
>> $ echo 'main() { }' > a.c; /bin/i686-w64-mingw32-gcc -m32 a.c
> /usr/bin/i686-w64-mingw32-ld: cannot find default-manifest.o

Please try again without the /bin/ prefix.
> Looks like it's not searching for the default-manifest.o in the correct
> include paths.
>> The mingw file resides in
> /usr/{x86_64,i686}-w64-mingw32/lib/
>> Maybe it should be in
> /usr/{x86_64,i686}-w64-mingw32/sys-root/mingw/lib/

The location is not the problem here.
> But the weird thing is that all those scripts in the ldscripts directory
> specify
> SEARCH_DIR("=/usr/x86_64-w64-mingw32/lib");
> so I'm not sure why this fails.

https://sourceware.org/bugzilla/show_bug.cgi?id=16792
But when linking with gcc it should be moot.
> I'm also experiencing the problems mentioned in the following thread:
> http://www.cygwin.com/ml/cygwin/2014-04/msg00016.html
>> In my case compiling putty/kitty from source using the latest binutils
> results in a broken "About" button. Clicking it simply does nothing, no
> about dialog appears at all.

https://sourceware.org/bugzilla/show_bug.cgi?id=16807
> Is there a way to disable that whole default-manifest.o thing for now
> without having to roll back to an older version of binutils?

No, you may have to roll back for now.
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple