https://sourceware.org/bugzilla/show_bug.cgi?id=32243
--- Comment #6 from oset ---
The patch (https://sourceware.org/bugzilla/attachment.cgi?id=15732&action=diff
@ https://sourceware.org/bugzilla/show_bug.cgi?id=32243#c1) uses 256.
--
You are receiving this mail because:
You are on the CC
https://sourceware.org/bugzilla/show_bug.cgi?id=32243
oset changed:
What|Removed |Added
CC||oset at superbox dot pl
--- Comment #4 from
https://sourceware.org/bugzilla/show_bug.cgi?id=31475
oset changed:
What|Removed |Added
CC||oset at superbox dot pl
--- Comment #2 from
> > you need to use --enable-64-bit-bfd Ok, I passed it to main
`configure' and it seems to work. Only, my old v2.32, which on old
computer, I wanted to regfresh, didn't seem to pass it to bfd, and
didn't compile it in.
> If you don't select a 64-bit target There is no such thing in
binutils' `configure', only in `bfd/configure'. > you need to
use --enable-64-bit-bfd. How exactly? ./configure && bfd/configure
or opposite or how?
Why is 32-bit objdump not able to read 64-bit executable?Whether it's
ELF or PE, it just reads binary structure of the file, so what is the problem
with enabling x64-executable read in x86 objdump?
