From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Akihiko Odaki" <akihiko.odaki@gmail.com>,
"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>
Subject: Re: [PULL v2 00/36] Testing, docs, semihosting and plugin updates
Date: Fri, 24 Feb 2023 09:16:21 +0100 [thread overview]
Message-ID: <1da14ae6-c03a-e87f-27b5-5851516e111c@linaro.org> (raw)
In-Reply-To: <b72ffae1-f640-cacb-ef47-b3593edb1bab@gmail.com>
On 24/2/23 05:51, Akihiko Odaki wrote:
> On 2023/02/23 21:59, Philippe Mathieu-Daudé wrote:
>> 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.
>
> I think this problem is tracked at:
> https://gitlab.com/qemu-project/qemu/-/issues/1244
>
> It is caused by linker flags Meson adds. For Meson, it is tracked at:
> https://github.com/mesonbuild/meson/issues/10894
Indeed. Thank you Akihiko :)
prev parent reply other threads:[~2023-02-24 8:16 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é
2023-02-24 4:51 ` Akihiko Odaki
2023-02-24 8:16 ` Philippe Mathieu-Daudé [this message]
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=1da14ae6-c03a-e87f-27b5-5851516e111c@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).