qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Fam Zheng <famz@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/12] RCU, scsi, modules, icount changes for 2015-01-30
Date: Mon, 02 Feb 2015 19:16:38 +0100	[thread overview]
Message-ID: <54CFBF06.3020401@redhat.com> (raw)
In-Reply-To: <CAFEAcA_NELNuiRxVL7Ze19DiJDCjedWn8JuLTNiLA5oVQ7rtjQ@mail.gmail.com>



On 02/02/2015 18:54, Peter Maydell wrote:
> On 2 February 2015 at 16:29, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> The important bits here are the first part of RCU and enabling
>> modules by default.  They have been tested with Travis for a few
>> days now, and things seem okay.
>>
>> v1->v2 changes are the new qemu-thread patch to fix Mac OS X,
>> and cleaning up warnings.
> 
> More build failures, I'm afraid:

Can you merge up to commit 2aeba9d8a1b6121b98948fcd42fd2aa32f68b750 only
or should I respin without the final patch?

Paolo

> Tools all fail to link in a static build:
> (exec '../../configure' '--cc=ccache gcc' '--enable-debug' '--static'
> '--disable-system')
> 
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o):
> In function `g_get_user_database_entry':
> (.text+0x245): warning: Using 'getpwuid' in statically linked
> applications requires at runtime the shared libraries from the glibc
> version used for linking
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o):
> In function `g_get_user_database_entry':
> (.text+0xa4): warning: Using 'getpwnam_r' in statically linked
> applications requires at runtime the shared libraries from the glibc
> version used for linking
> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o):
> In function `g_get_user_database_entry':
> (.text+0xdb): warning: Using 'getpwuid_r' in statically linked
> applications requires at runtime the shared libraries from the glibc
> version used for linking
> /usr/bin/ld: dynamic STT_GNU_IFUNC symbol `strcmp' with pointer
> equality in `/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libc.a(strcmp.o)'
> cannot be used when making an executable; recompile with -fPIE and
> relink with -pie
> collect2: error: ld returned 1 exit status
> make: *** [qemu-bridge-helper] Error 1
> 
> Module linking fails on ARM host:
>   LINK  block/curl.so
> /usr/bin/ld: block/curl.o: relocation R_ARM_THM_MOVW_ABS_NC against
> `__stack_chk_guard' can not be used when making a shared object;
> recompile with -fPIC
> block/curl.o: could not read symbols: Bad value
> collect2: error: ld returned 1 exit status
> 
> -- PMM
> 
> 

  reply	other threads:[~2015-02-02 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:29 [Qemu-devel] [PULL v2 00/12] RCU, scsi, modules, icount changes for 2015-01-30 Paolo Bonzini
2015-02-02 17:54 ` Peter Maydell
2015-02-02 18:16   ` Paolo Bonzini [this message]
2015-02-02 18:24     ` Peter Maydell

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=54CFBF06.3020401@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=peter.maydell@linaro.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).