From: "John L. Poole" <jlpoole56@gmail.com>
To: xen-devel@lists.xen.org
Subject: [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous
Date: Wed, 7 Dec 2016 07:57:02 -0800 [thread overview]
Message-ID: <67b30376-49cb-3d16-c208-6bba78b5ecc1@gmail.com> (raw)
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
next reply other threads:[~2016-12-07 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 15:57 John L. Poole [this message]
2016-12-07 16:51 ` [BUG] Xen-4.8.0 efi/buildid.o: file not recognized/Ambiguous 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67b30376-49cb-3d16-c208-6bba78b5ecc1@gmail.com \
--to=jlpoole56@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).