qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [FYI] Need to do a full rebuild if you are on Linux x86 host
Date: Tue, 22 Nov 2011 10:41:14 +0100	[thread overview]
Message-ID: <4ECB6E3A.2000804@redhat.com> (raw)
In-Reply-To: <4ECAEBDD.2070805@codemonkey.ws>

On 11/22/11 01:25, Anthony Liguori wrote:
> Due to this commit:
> 
> commit 40d6444e91c6ab17e5e8ab01d4eece90cbc4afed
> Author: Avi Kivity <avi@redhat.com>
> Date:   Tue Nov 15 20:12:17 2011 +0200
> 
>     configure: build position independent executables on x86-Linux hosts
> 
> PIE binaries cannot be linked with non-PIE binaries and make is not
> smart enough to rebuild when the CFLAGS have changed.

Breaks build on RHEL-5 and probably also other not-so-recent linux distros.

[ ... ]
  CC    i386-softmmu/exec.o
[ ... ]
  LINK  i386-softmmu/qemu-system-i386
/usr/bin/ld: exec.o: relocation R_X86_64_TPOFF32 against
`tls__cpu_single_env' can not be used when making a shared object;
recompile with -fPIC
exec.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[1]: *** [qemu-system-i386] Error 1
make: *** [subdir-i386-softmmu] Error 2

cheers,
  Gerd

PS: for those with ipv6 connectivity the full log is available at
http://spunk.home.kraxel.org/bb/builders/rhel5-default/builds/98/steps/compile/logs/stdio

  reply	other threads:[~2011-11-22  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  0:25 [Qemu-devel] [FYI] Need to do a full rebuild if you are on Linux x86 host Anthony Liguori
2011-11-22  9:41 ` Gerd Hoffmann [this message]
2011-11-22 10:01   ` Paolo Bonzini
2011-11-22 10:05     ` Avi Kivity

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=4ECB6E3A.2000804@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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).