https://sourceware.org/bugzilla/show_bug.cgi?id=1198
Lionel Debroux <lionel_debroux at yahoo dot fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Lionel Debroux <lionel_debroux at yahoo dot fr> ---
Alright, I've now been able to spend some time setting up 32-bit Cygwin on a
Windows computer (Win 7 x64 VM), and building several binutils versions :)
The results are as follows:
* for sanity checking: binutils 2.16.1a, successfully built by Cygwin GCC
5.2.0, segfaults on the file I posted 10 years ago if its prefix is
/tmp/m68k-coff-binutils or /tmp/m68k-coff-binu2161, but reports invalid
relocation data and exits with proper 1 value if the prefix is /home/<7-letter
username>/prefix/m68k-coff-binutils2161.
* binutils 2.25.1 (need to use -i for make) doesn't barf, when installed at
/tmp/m68k-coff-binutils, /tmp/m68k-coff-binu2251 or /home/<7-letter
username>/prefix/m68k-coff-binutils2251: they print that the file contains
invalid relocation data, as binutils 2.16 did under Linux (with unknown prefix)
10 years ago.
* binutils 2.21.1, 2.22, 2.23.2 don't build under that setup, even with make
-i;
* binutils 2.24 didn't barf at /home/<7-letter
username>/prefix/m68k-coff-binutils224, I haven't tested
/tmp/m68k-coff-binutils or /tmp/m68k-coff-binut224.
I suppose I'll mark this bug resolved, all the more the m68k-coff
(m68k-unknown-coff) target was made unsupported for gas years ago :)
--
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
