[Bug go/63539] New: libgo does not use the newly built objcopy when doing a combined build
pinskia at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Wed Oct 15 02:09:00 GMT 2014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63539
Bug ID: 63539
Summary: libgo does not use the newly built objcopy when doing
a combined build
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: pinskia at gcc dot gnu.org
CC: cmang at google dot com
I was trying build a go compiler for aarch46 and ran into this issue.
I was doing a full combined build with all of GCC/binutils from the trunk.
f=`echo container/ring.lo | sed -e 's/.lo$/.o/'`; objcopy -j .go_export $f
container/ring.gox.tmp && mv -f container/ring.gox.tmp container/ring.gox
objcopy: Unable to recognise the format of the input file `container/ring.o'
In this case container/ring.o is an aarch64 elf binary and my host objcopy
(2.20) does not understand aarch64 elf files.
More information about the Gcc-bugs
mailing list