On 12/9/2016 12:03 AM, Jan Beulich wrote:
On 08.12.16 at 20:35, <jlpool...@gmail.com> wrote:
On 12/7/2016 8:51 AM, Jan Beulich wrote:
On 07.12.16 at 16:57, <jlpool...@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