https://sourceware.org/bugzilla/show_bug.cgi?id=16790
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from Nick Clifton <nickc at redhat dot com> ---
I have uploaded a potential fix for the problem. Please give it a try.
I am uncertain as to whether this is the right thing to do however. Maybe it
would be better to rethink the whole
linker-is-responsible-for-adding-the-default-manifest idea. IMHO it would be
better if gcc/libgcc did this - after all it already has the multilib mechanism
in place and it already builds files like crt0.o and crtend.o. Why not add
default-manifest.o to the list ? The answer, as I understand it, is that the
cygwin developers want the manifest added even if gcc is not used to link the
application. So maybe it is time to impose a requirement to use gcc to link
all cygwin and mingw binaries ?
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-binutils
