From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org,
"Richard Henderson" <richard.henderson@linaro.org>,
"Emilio Cota" <cota@braap.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Akihiko Odaki" <akihiko.odaki@gmail.com>
Subject: Re: [PULL v2 00/36] Testing, docs, semihosting and plugin updates
Date: Thu, 23 Feb 2023 13:59:27 +0100 [thread overview]
Message-ID: <0d17e82c-4226-84fb-9301-644935d326e4@linaro.org> (raw)
In-Reply-To: <01d13cc2-f346-71a7-d941-2d1a0dc42514@linaro.org>
On 3/2/23 18:38, Philippe Mathieu-Daudé wrote:
> On 2/2/23 17:01, Alex Bennée wrote:
>> ----------------------------------------------------------------
>> Testing, docs, semihosting and plugin updates
>> ----------------------------------------------------------------
> FTR I'm now seeing this warning on Darwin/Aarch64:
>
> C compiler for the host machine: clang (clang 14.0.0 "Apple clang
> version 14.0.0 (clang-1400.0.29.202)")
> C linker for the host machine: clang ld64 820.1
> Host machine cpu family: aarch64
> Host machine cpu: aarch64
> ...
> [1/3253] Linking target tests/plugin/libbb.dylib
> ld: warning: -undefined dynamic_lookup may not work with chained fixups
> [2/3253] Linking target tests/plugin/libinsn.dylib
> ld: warning: -undefined dynamic_lookup may not work with chained fixups
> [3/3253] Linking target tests/plugin/libmem.dylib
> ld: warning: -undefined dynamic_lookup may not work with chained fixups
> [4/3253] Linking target tests/plugin/libsyscall.dylib
> ld: warning: -undefined dynamic_lookup may not work with chained fixups
Googling, someone suggest to use --linkopt=-Wl,-no_fixup_chains:
https://github.com/bazelbuild/bazel/issues/16413#issuecomment-1270603343
This doesn't show up on GitLab which uses:
C compiler for the host machine: cc (clang 13.1.6 "Apple clang version
13.1.6 (clang-1316.0.21.2.5)")
C linker for the host machine: cc ld64 764
Host machine cpu family: aarch64
Host machine cpu: aarch64
I guess I'll just ignore these warnings.
next prev parent reply other threads:[~2023-02-23 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 16:01 [PULL v2 00/36] Testing, docs, semihosting and plugin updates Alex Bennée
2023-02-03 9:30 ` Peter Maydell
2023-02-03 17:38 ` Philippe Mathieu-Daudé
2023-02-23 12:59 ` Philippe Mathieu-Daudé [this message]
2023-02-24 4:51 ` Akihiko Odaki
2023-02-24 8:16 ` Philippe Mathieu-Daudé
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=0d17e82c-4226-84fb-9301-644935d326e4@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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 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).