From: "Marc Marí" <markmb@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Gabriel L. Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, Kevin O'Connor <kevin@koconnor.net>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Laszlo <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] Add optionrom compatible with fw_cfg DMA version
Date: Tue, 26 Jan 2016 12:20:04 +0100 [thread overview]
Message-ID: <20160126122004.0798fd71@markmb_rh> (raw)
In-Reply-To: <20160126111154.GA14533@stefanha-x1.localdomain>
On Tue, 26 Jan 2016 11:11:54 +0000
Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Mon, Jan 25, 2016 at 02:17:48PM +0100, Marc Marí wrote:
> > +linuxboot_dma.img: linuxboot_dma.o
> > + $(call quiet-command,$(LD) $(LDFLAGS_NOPIE) -m elf_i386
> > -Ttext 0 -e _start -s -o $@ $<," Building $(TARGET_DIR)$@") +
> > %.img: %.o
> > $(call quiet-command,$(LD) $(LDFLAGS_NOPIE) -Ttext 0 -e
> > _start -s -o $@ $<," Building $(TARGET_DIR)$@")
>
> Why is -m elf_i386 necessary for linuxboot_dma.img but not for the
> other *.img files?
I cannot give a precise explanation. But if I don't force an output
type, I get this error:
Building optionrom/linuxboot_dma.img
ld: i386 architecture of input file `linuxboot_dma.o' is incompatible
with i386:x86-64 output
Marc
next prev parent reply other threads:[~2016-01-26 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 13:17 [Qemu-devel] [PATCH v3] Add optionrom compatible with fw_cfg DMA version Marc Marí
2016-01-26 11:11 ` Stefan Hajnoczi
2016-01-26 11:20 ` Marc Marí [this message]
2016-01-26 11:26 ` Gerd Hoffmann
2016-01-27 16:43 ` Stefan Hajnoczi
2016-01-27 16:57 ` Marc Marí
2016-01-27 17:17 ` Kevin O'Connor
2016-01-28 10:18 ` Marc Marí
2016-01-28 10:55 ` Stefan Hajnoczi
2016-01-28 0:14 ` Kevin O'Connor
2016-01-28 11:20 ` Marc Marí
2016-01-28 15:24 ` Kevin O'Connor
2016-01-28 21:06 ` Marc Marí
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=20160126122004.0798fd71@markmb_rh \
--to=markmb@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
--cc=stefanha@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.