* [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous
@ 2016-12-07 15:57 John L. Poole
2016-12-07 16:51 ` Jan Beulich
2016-12-22 14:46 ` Jan Beulich
0 siblings, 2 replies; 10+ messages in thread
From: John L. Poole @ 2016-12-07 15:57 UTC (permalink / raw)
To: xen-devel
I did the the following:
wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz
tar -xvzf xen-4.8.0.tar.gz
cd /usr/local/src/xen-4.8.0
./configure
The config.log is available at: http://napadata.net/paste/view/9e7faf3d
make
...
mv -f .efi.lds.d.new .efi.lds.d
gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc
efi/mkreloc.c
ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000
--stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000
--file-alignment=0x20 --major-image-version=4 --minor-image-version=8
--major-os-version=2 --minor-os-version=0 --major-subsystem-version=2
--minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o
efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o
efi/buildid.o -o
/usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld
-mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0
--heap=0,0 --strip-debug --section-alignment=0x200000
--file-alignment=0x20 --major-image-version=4 --minor-image-version=8
--major-os-version=2 --minor-os-version=0 --major-subsystem-version=2
--minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o
efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o
efi/buildid.o -o
/usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && :
efi/buildid.o: file not recognized: File format is ambiguous
efi/buildid.o: matching formats: coff-x86-64 pe-x86-64
Makefile:175: recipe for target
'/usr/local/src/xen-4.8.0/xen/xen.efi' failed
make[3]: *** [/usr/local/src/xen-4.8.0/xen/xen.efi] Error 1
make[3]: Leaving directory '/usr/local/src/xen-4.8.0/xen/arch/x86'
Makefile:135: recipe for target '/usr/local/src/xen-4.8.0/xen/xen'
failed
make[2]: *** [/usr/local/src/xen-4.8.0/xen/xen] Error 2
make[2]: Leaving directory '/usr/local/src/xen-4.8.0/xen'
Makefile:45: recipe for target 'install' failed
make[1]: *** [install] Error 2
make[1]: Leaving directory '/usr/local/src/xen-4.8.0/xen'
Makefile:97: recipe for target 'install-xen' failed
make: *** [install-xen] Error 2
jlpoole@zeta /usr/local/src/xen-4.8.0 $
I can post anything other information requested in my pastebin or
provide as directed. I would have opened a bug, but
https://wiki.xenproject.org/wiki/Reporting_Bugs_against_Xen_Project
suggests sending to this list first.
John Poole
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-07 15:57 [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous John L. Poole @ 2016-12-07 16:51 ` Jan Beulich 2016-12-07 17:01 ` John L. Poole 2016-12-08 19:35 ` John L. Poole 2016-12-22 14:46 ` Jan Beulich 1 sibling, 2 replies; 10+ messages in thread From: Jan Beulich @ 2016-12-07 16:51 UTC (permalink / raw) To: jlpoole56; +Cc: xen-devel >>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: > I did the the following: > > wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz > tar -xvzf xen-4.8.0.tar.gz > cd /usr/local/src/xen-4.8.0 > ./configure > > The config.log is available at: http://napadata.net/paste/view/9e7faf3d > > > make > > ... > mv -f .efi.lds.d.new .efi.lds.d > gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer > -fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc > efi/mkreloc.c > ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000 > --stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000 > --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 > --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 > --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o > efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o > efi/buildid.o -o > /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld > -mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0 > --heap=0,0 --strip-debug --section-alignment=0x200000 > --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 > --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 > --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o > efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o > efi/buildid.o -o > /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && : > efi/buildid.o: file not recognized: File format is ambiguous > efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 Hmm, at the first glance I'd call this a binutils bug: When talking about an object file, it's necessarily COFF and never PE. But I'd have to study their logic first to be certain. What binutils version are you using, and what's the target list e.g. objcopy lists at the end of its --help output? Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-07 16:51 ` Jan Beulich @ 2016-12-07 17:01 ` John L. Poole 2016-12-08 19:35 ` John L. Poole 1 sibling, 0 replies; 10+ messages in thread From: John L. Poole @ 2016-12-07 17:01 UTC (permalink / raw) To: Jan Beulich; +Cc: xen-devel On 12/7/2016 8:51 AM, Jan Beulich wrote: >>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >> I did the the following: >> >> wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz >> tar -xvzf xen-4.8.0.tar.gz >> cd /usr/local/src/xen-4.8.0 >> ./configure >> >> The config.log is available at: http://napadata.net/paste/view/9e7faf3d >> >> >> make >> >> ... >> mv -f .efi.lds.d.new .efi.lds.d >> gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer >> -fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc >> efi/mkreloc.c >> ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000 >> --stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000 >> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >> efi/buildid.o -o >> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld >> -mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0 >> --heap=0,0 --strip-debug --section-alignment=0x200000 >> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >> efi/buildid.o -o >> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && : >> efi/buildid.o: file not recognized: File format is ambiguous >> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 > Hmm, at the first glance I'd call this a binutils bug: When talking > about an object file, it's necessarily COFF and never PE. But I'd > have to study their logic first to be certain. What binutils version > are you using, and what's the target list e.g. objcopy lists at the > end of its --help output? > > Jan > Jan - 1) bintuils version: 2.25.1-r1 jlpoole@zeta /boot/efi $ eix binutils -I [I] sys-devel/binutils Available versions: ... Installed versions: 2.25.1-r1(2.25.1)(06:01:52 AM 11/12/2016)(cxx multitarget nls zlib -static-libs -test -vanilla) Homepage: https://sourceware.org/binutils/ Description: Tools necessary to build programs 2) target list from the output of "objcopy --help" is located at: http://napadata.net/paste/view/6ebf2472 Thank you, John _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-07 16:51 ` Jan Beulich 2016-12-07 17:01 ` John L. Poole @ 2016-12-08 19:35 ` John L. Poole 2016-12-09 0:47 ` Håkon Alstadheim 2016-12-09 8:03 ` Jan Beulich 1 sibling, 2 replies; 10+ messages in thread From: John L. Poole @ 2016-12-08 19:35 UTC (permalink / raw) To: Jan Beulich; +Cc: xen-devel [-- Attachment #1.1: Type: text/plain, Size: 2162 bytes --] On 12/7/2016 8:51 AM, Jan Beulich wrote: >>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >> I did the the following: >> >> wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz >> tar -xvzf xen-4.8.0.tar.gz >> cd /usr/local/src/xen-4.8.0 >> ./configure >> >> The config.log is available at: http://napadata.net/paste/view/9e7faf3d >> >> >> make >> >> ... >> mv -f .efi.lds.d.new .efi.lds.d >> gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer >> -fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc >> efi/mkreloc.c >> ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000 >> --stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000 >> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >> efi/buildid.o -o >> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld >> -mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0 >> --heap=0,0 --strip-debug --section-alignment=0x200000 >> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >> efi/buildid.o -o >> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && : >> efi/buildid.o: file not recognized: File format is ambiguous >> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 > Hmm, at the first glance I'd call this a binutils bug: When talking > about an object file, it's necessarily COFF and never PE. But I'd > have to study their logic first to be certain. What binutils version > are you using, and what's the target list e.g. objcopy lists at the > end of its --help output? > > Jan > I updated my binutils to 2.27 and I successfully completed "make". Thank you. John [-- Attachment #1.2: Type: text/html, Size: 3099 bytes --] [-- Attachment #2: Type: text/plain, Size: 127 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-08 19:35 ` John L. Poole @ 2016-12-09 0:47 ` Håkon Alstadheim 2016-12-09 8:03 ` Jan Beulich 1 sibling, 0 replies; 10+ messages in thread From: Håkon Alstadheim @ 2016-12-09 0:47 UTC (permalink / raw) To: xen-devel Den 08. des. 2016 20:35, skrev John L. Poole: > > > On 12/7/2016 8:51 AM, Jan Beulich wrote: >>>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >>> I did the the following: >>> >>> wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz >>> tar -xvzf xen-4.8.0.tar.gz >>> cd /usr/local/src/xen-4.8.0 >>> ./configure >>> >>> The config.log is available at: http://napadata.net/paste/view/9e7faf3d >>> >>> >>> make >>> >>> ... >>> mv -f .efi.lds.d.new .efi.lds.d >>> gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer >>> -fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc >>> efi/mkreloc.c >>> ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000 >>> --stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000 >>> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >>> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >>> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >>> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >>> efi/buildid.o -o >>> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld >>> -mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0 >>> --heap=0,0 --strip-debug --section-alignment=0x200000 >>> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >>> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >>> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >>> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >>> efi/buildid.o -o >>> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && : >>> efi/buildid.o: file not recognized: File format is ambiguous >>> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 >> Hmm, at the first glance I'd call this a binutils bug: When talking >> about an object file, it's necessarily COFF and never PE. But I'd >> have to study their logic first to be certain. What binutils version >> are you using, and what's the target list e.g. objcopy lists at the >> end of its --help output? >> >> Jan >> > > I updated my binutils to 2.27 and I successfully completed "make". > Thank you. > I have the same problem with binutils-2.27 on gentoo. Worked around it by adding " -b coff-x86-64 " to the ld command line before $(note_file). Running with gentoo-sources-4.8.12-gentoo-r1 as dom0 kernel. Compiled with gcc set to x86_64-pc-linux-gnu-5.4.0 . Apart from that seems to be running nicely, in early test :-) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-08 19:35 ` John L. Poole 2016-12-09 0:47 ` Håkon Alstadheim @ 2016-12-09 8:03 ` Jan Beulich 2016-12-09 14:25 ` John L. Poole 1 sibling, 1 reply; 10+ messages in thread From: Jan Beulich @ 2016-12-09 8:03 UTC (permalink / raw) To: jlpoole56; +Cc: xen-devel >>> On 08.12.16 at 20:35, <jlpoole56@gmail.com> wrote: > > On 12/7/2016 8:51 AM, Jan Beulich wrote: >>>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >>> I did the the following: >>> >>> wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz >>> tar -xvzf xen-4.8.0.tar.gz >>> cd /usr/local/src/xen-4.8.0 >>> ./configure >>> >>> The config.log is available at: http://napadata.net/paste/view/9e7faf3d >>> >>> >>> make >>> >>> ... >>> mv -f .efi.lds.d.new .efi.lds.d >>> gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer >>> -fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc >>> efi/mkreloc.c >>> ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000 >>> --stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000 >>> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >>> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >>> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >>> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >>> efi/buildid.o -o >>> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld >>> -mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0 >>> --heap=0,0 --strip-debug --section-alignment=0x200000 >>> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >>> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >>> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >>> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >>> efi/buildid.o -o >>> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && : >>> efi/buildid.o: file not recognized: File format is ambiguous >>> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 >> Hmm, at the first glance I'd call this a binutils bug: When talking >> about an object file, it's necessarily COFF and never PE. But I'd >> have to study their logic first to be certain. What binutils version >> are you using, and what's the target list e.g. objcopy lists at the >> end of its --help output? > > I updated my binutils to 2.27 and I successfully completed "make". Thank > you. Good to know. Is that newer version similarly configured, or is your success simply because of the two conflicting target types not being there at the same time? Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-09 8:03 ` Jan Beulich @ 2016-12-09 14:25 ` John L. Poole 0 siblings, 0 replies; 10+ messages in thread From: John L. Poole @ 2016-12-09 14:25 UTC (permalink / raw) To: Jan Beulich; +Cc: xen-devel On 12/9/2016 12:03 AM, Jan Beulich wrote: >>>> On 08.12.16 at 20:35, <jlpoole56@gmail.com> wrote: >> On 12/7/2016 8:51 AM, Jan Beulich wrote: >>>>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >>>> I did the the following: >>>> >>>> wget https://downloads.xenproject.org/release/xen/4.8.0/xen-4.8.0.tar.gz >>>> tar -xvzf xen-4.8.0.tar.gz >>>> cd /usr/local/src/xen-4.8.0 >>>> ./configure >>>> >>>> The config.log is available at: http://napadata.net/paste/view/9e7faf3d >>>> >>>> >>>> make >>>> >>>> ... >>>> mv -f .efi.lds.d.new .efi.lds.d >>>> gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer >>>> -fno-strict-aliasing -Wdeclaration-after-statement -g -o efi/mkreloc >>>> efi/mkreloc.c >>>> ld -mi386pep --subsystem=10 --image-base=0xffff82d080000000 >>>> --stack=0,0 --heap=0,0 --strip-debug --section-alignment=0x200000 >>>> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >>>> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >>>> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >>>> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >>>> efi/buildid.o -o >>>> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d080000000.0 && ld >>>> -mi386pep --subsystem=10 --image-base=0xffff82d0c0000000 --stack=0,0 >>>> --heap=0,0 --strip-debug --section-alignment=0x200000 >>>> --file-alignment=0x20 --major-image-version=4 --minor-image-version=8 >>>> --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 >>>> --minor-subsystem-version=0 --build-id=sha1 -T efi.lds -N prelink-efi.o >>>> efi/relocs-dummy.o /usr/local/src/xen-4.8.0/xen/common/symbols-dummy.o >>>> efi/buildid.o -o >>>> /usr/local/src/xen-4.8.0/xen/.xen.efi.0xffff82d0c0000000.0 && : >>>> efi/buildid.o: file not recognized: File format is ambiguous >>>> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 >>> Hmm, at the first glance I'd call this a binutils bug: When talking >>> about an object file, it's necessarily COFF and never PE. But I'd >>> have to study their logic first to be certain. What binutils version >>> are you using, and what's the target list e.g. objcopy lists at the >>> end of its --help output? >> I updated my binutils to 2.27 and I successfully completed "make". Thank >> you. > Good to know. Is that newer version similarly configured, or is > your success simply because of the two conflicting target types > not being there at the same time? > > Jan > Jan, you raised an interesting issue. Now when I try to compile Xen 4.8.0 using Gentoo's portage command "emerge", I'm getting the error I originally had, "File format is ambiguous", that brought me to this list. Thinking it was because I had both versions of binutils on my system (slotted), I assumed Gentoo's emerge was failing because it was invoking the earlier version of binutils. So I removed the earlier version of binutils (2.25.1-r10) leaving only binutils 2.27 in my environment. Still, when I went to compile using Portage with: USE="efi" emerge app-emulation/xen I ran into the same problem: "File format is ambiguous". This bug is documented at: Gentoo Bug 602052 - app-emulation/xen-4.8.0 Makefile:141: recipe for target fails at https://bugs.gentoo.org/show_bug.cgi?id=602052 I then returned to /usr/local/src/xen-4.8.0 and executed: make world which would clean and try again. Now I've encountered the same error. Previously, I had performed make, encountered the error and came to this list. I then added binutils 2.27 and did "make" again (no clean) and the build succeeded. So I am guessing that some files from my first attempt at make were cached and on the second attempt (without clean) the problem did not occur. Now that I have done a "make world", I tried "make" again to simulate the events up to my success at buildling the first time. This time I was stopped at the same point: "File format is ambiguous". Now I am at a loss to understand why I was able to build one time, but not now. The log files of the sessions are as follows: Outside Gentoo Portage: "make world": http://napadata.net/paste/view/eb7c1d97 "make" 2nd: http://napadata.net/paste/view/6463bc22 Gentoo: USE="efi" emerge app-emulation/xen: http://napadata.net/paste/view/0fb9f9fd I did use "-j9" to speed things up. - John _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-07 15:57 [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous John L. Poole 2016-12-07 16:51 ` Jan Beulich @ 2016-12-22 14:46 ` Jan Beulich 2017-01-05 15:09 ` Doug Goldstein 1 sibling, 1 reply; 10+ messages in thread From: Jan Beulich @ 2016-12-22 14:46 UTC (permalink / raw) To: jlpoole56; +Cc: xen-devel >>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: > efi/buildid.o: file not recognized: File format is ambiguous > efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 Just fyi: After some analysis of the binutils sources I have come to the conclusion that this needs help from the binutils folks. I've just sent https://sourceware.org/ml/binutils/2016-12/msg00374.html to see if they have any advice. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2016-12-22 14:46 ` Jan Beulich @ 2017-01-05 15:09 ` Doug Goldstein 2017-01-05 15:21 ` Jan Beulich 0 siblings, 1 reply; 10+ messages in thread From: Doug Goldstein @ 2017-01-05 15:09 UTC (permalink / raw) To: Jan Beulich, jlpoole56; +Cc: xen-devel [-- Attachment #1.1.1: Type: text/plain, Size: 721 bytes --] On 12/22/16 8:46 AM, Jan Beulich wrote: >>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >> efi/buildid.o: file not recognized: File format is ambiguous >> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 > > Just fyi: After some analysis of the binutils sources I have come to > the conclusion that this needs help from the binutils folks. I've just > sent > https://sourceware.org/ml/binutils/2016-12/msg00374.html > to see if they have any advice. > Has anything come of this? I'm not sure how we can use match_priority or if they're saying they need to make changes to binutils. At this point I'm not able to compile Xen myself without local hackery. -- Doug Goldstein [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 959 bytes --] [-- Attachment #2: Type: text/plain, Size: 127 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 2017-01-05 15:09 ` Doug Goldstein @ 2017-01-05 15:21 ` Jan Beulich 0 siblings, 0 replies; 10+ messages in thread From: Jan Beulich @ 2017-01-05 15:21 UTC (permalink / raw) To: Doug Goldstein; +Cc: jlpoole56, xen-devel >>> On 05.01.17 at 16:09, <cardoe@cardoe.com> wrote: > On 12/22/16 8:46 AM, Jan Beulich wrote: >>>>> On 07.12.16 at 16:57, <jlpoole56@gmail.com> wrote: >>> efi/buildid.o: file not recognized: File format is ambiguous >>> efi/buildid.o: matching formats: coff-x86-64 pe-x86-64 >> >> Just fyi: After some analysis of the binutils sources I have come to >> the conclusion that this needs help from the binutils folks. I've just >> sent >> https://sourceware.org/ml/binutils/2016-12/msg00374.html >> to see if they have any advice. >> > > Has anything come of this? I'm not sure how we can use match_priority or > if they're saying they need to make changes to binutils. At this point > I'm not able to compile Xen myself without local hackery. As said on irc, I don't see how the responses we've got so far allow for progress towards a resolution. However, I also don't see the value of building binutils in this way, as COFF objects - afaict - would simply be unusable (without command line override) for anyone else too. So besides the option of us hacking around the issue, I'd like distro maintainers of binutils packages to consider correcting their ./configure options, to produce something that's actually usable. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2017-01-05 15:21 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-12-07 15:57 [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous John L. Poole 2016-12-07 16:51 ` Jan Beulich 2016-12-07 17:01 ` John L. Poole 2016-12-08 19:35 ` John L. Poole 2016-12-09 0:47 ` Håkon Alstadheim 2016-12-09 8:03 ` Jan Beulich 2016-12-09 14:25 ` John L. Poole 2016-12-22 14:46 ` Jan Beulich 2017-01-05 15:09 ` Doug Goldstein 2017-01-05 15:21 ` Jan Beulich
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).