https://sourceware.org/bugzilla/show_bug.cgi?id=1198
--- Comment #3 from Lionel Debroux <lionel_debroux at yahoo dot fr> --- I had completely forgotten about this bug report posted several days after I first installed Linux on my computer :) In the meantime: * I switched to Linux near-full-time in 2006, for both home and work usage. This computer cannot easily run VirtualBox VMs anymore. The simplest way to perform native Windows builds and tests is now to use another computer from work, which could take a bit of time, possibly not before the end of next week. * I co-created the GCC4TI development environment out of the aforementioned TIGCC. Among the various bugfixes and improvements we made, the following ones are relevant to this discussion: 1) the custom build scripts do not delete ar, objcopy, objdump, size and strip any longer (better having incomplete tools for expert usage than none at all !); 2) GCC4TI's gcc and binutils use a program prefix, so that they don't collide with system gcc and binutils; 3) the local patch to binutils was expanded one hack-ish hunk, so as to mask out the offending flag and make the binutils more usable, though not necessarily in the way upstream would do it. See the first hunk of https://github.com/debrouxl/gcc4ti/blob/4a0341f02f9d95a205b8601ca7be39cd876c5b1c/trunk/tigcc/gcc/gas-2.16-tigcc-patch.diff . * binutils, like many other programs, went through rounds of fuzzing and subsequent bugfixing, while GCC's Windows support further improved. The problem might therefore well be gone from modern binutils versions, only testing will tell - but I can't do that today :) -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils