qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 00/12] testing and plugin fixes
Date: Thu, 28 May 2020 16:09:52 +0100	[thread overview]
Message-ID: <CAFEAcA_QTkWA7eBwORWMmpcH1E5bF4A3mFtkzdstkucd-2+p3A@mail.gmail.com> (raw)
In-Reply-To: <87blm83y5v.fsf@linaro.org>

On Thu, 28 May 2020 at 15:57, Alex Bennée <alex.bennee@linaro.org> wrote:
> I get these on commit ddc760832fa8cf5e93b9d9e6e854a5114ac63510:
>
>     LINK    arm-softmmu/qemu-system-arm
>   ld: /usr/lib/libc.so and /usr/lib/crt0.o: warning: multiple common of `environ'
>   ld: warning: libintl.so.1, needed by /usr/pkg/lib/libgio-2.0.so, may conflict with libintl.so.8
>   ld: warning: libintl.so.1, needed by /usr/pkg/lib/libgio-2.0.so, may conflict with libintl.so.8
>   ld: warning: libintl.so.1, needed by /usr/pkg/lib/libgio-2.0.so, may conflict with libintl.so.8
>   ld: warning: libintl.so.1, needed by /usr/pkg/lib/libgio-2.0.so, may conflict with libintl.so.8
>   ld: warning: libintl.so.1, needed by /usr/pkg/lib/libgio-2.0.so, may conflict with libintl.so.8
>
> which makes me think the build environment has changed and it was simply
> that my PR triggered a re-build of the NetBSD VM.

Yes. I see them also now on the next pullreq I'm trying to
process. How do I get back to an environment that doesn't
produce all these warnings?

thanks
-- PMM


  reply	other threads:[~2020-05-28 15:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 14:54 [PULL 00/12] testing and plugin fixes Alex Bennée
2020-05-27 14:54 ` [PULL 01/12] configure: add alternate binary for genisoimage Alex Bennée
2020-05-27 14:54 ` [PULL 02/12] tests/vm: pass --genisoimage to basevm script Alex Bennée
2020-05-27 14:54 ` [PULL 03/12] travis.yml: Use clang++ in the Clang tests Alex Bennée
2020-05-27 14:54 ` [PULL 04/12] tests/tcg: fix invocation of the memory record/replay tests Alex Bennée
2020-05-27 14:54 ` [PULL 05/12] tests/fp: enable extf80_le_quite tests Alex Bennée
2020-05-27 14:54 ` [PULL 06/12] tests/fp: split and audit the conversion tests Alex Bennée
2020-05-27 14:54 ` [PULL 07/12] tests/tcg: better detect confused gdb which can't connect Alex Bennée
2020-05-27 14:54 ` [PULL 08/12] tests/docker: add debian11 base image Alex Bennée
2020-05-27 14:54 ` [PULL 09/12] tests/docker: use a gcc-10 based image for arm64 tests Alex Bennée
2020-05-27 14:54 ` [PULL 10/12] cpus-common: ensure auto-assigned cpu_indexes don't clash Alex Bennée
2020-05-27 14:54 ` [PULL 11/12] linux-user: properly "unrealize" vCPU object Alex Bennée
2020-05-27 14:54 ` [PULL 12/12] tests/tcg: add new threadcount test Alex Bennée
2020-05-28 13:54 ` [PULL 00/12] testing and plugin fixes Peter Maydell
2020-05-28 14:16   ` Alex Bennée
2020-05-28 14:57   ` Alex Bennée
2020-05-28 15:09     ` Peter Maydell [this message]
2020-05-28 15:18       ` Philippe Mathieu-Daudé
2020-05-28 15:20         ` Peter Maydell
2020-05-28 15:26           ` Philippe Mathieu-Daudé
2020-05-28 16:07             ` Peter Maydell
2020-05-28 17:19           ` Alex Bennée
2020-05-28 15:38         ` Gerd Hoffmann
2020-05-29 18:25 ` 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=CAFEAcA_QTkWA7eBwORWMmpcH1E5bF4A3mFtkzdstkucd-2+p3A@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@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).