From: Claudio Fontana <cfontana@suse.de>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: help with a build-user and build-user-plugin failure
Date: Wed, 25 Nov 2020 13:00:17 +0100 [thread overview]
Message-ID: <6efbff12-a10b-8e55-908b-f2233fc8001e@suse.de> (raw)
In-Reply-To: <871rghixhb.fsf@linaro.org>
Hi Alex,
On 11/25/20 10:42 AM, Alex Bennée wrote:
>
> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>
>> On 11/24/20 12:04 PM, Claudio Fontana wrote:
>>> Hi Alex,
>>>
>>> I am seeing build failures with build-user and build-user-plugin:
>>>
>>> https://gitlab.com/hw-claudio/qemu/-/pipelines/220245998
>>>
>>> and I am trying to start investigating.
>>>
>>> How do I reproduce this locally?
>>>
>>> I am trying to run locally the check-tcg rule, but I cannot get it to work.
>>> I managed to work around the problem of static libraries (disabled them),
>>>
>>> but then I get:
>>>
>>> BUILD TCG tests for x86_64-linux-user
>>> BUILD x86_64-linux-user guest-tests with cc
>>> /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /tmp/ccgqtAM9.o: in function `test_fops':
>>> /dev/shm/cfontana/qemu/tests/tcg/i386/test-i386.c:759: undefined reference to `fmod'
>>> /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /dev/shm/cfontana/qemu/tests/tcg/i386/test-i386.c:760: undefined reference to `sqrt'
>>> /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /dev/shm/cfontana/qemu/tests/tcg/i386/test-i386.c:761: undefined reference to `sin'
>>> /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /dev/shm/cfontana/qemu/tests/tcg/i386/test-i386.c:762: undefined reference to `cos'
>>>
>>> Have you seen it before?
>>> Any suggestions? I'm on OpenSUSE Leap 15 SP2.
>>
>> Related to 3fc1aad3864 ("configure: remove unnecessary libm test")
>> + tcg tests still not ported to Meson?
>
> Hmm so we certainly need libm for the testcase but I guess this is> failing with a local cross compiler rather than docker? I'm not sure the
> global feature test should be relevant for testcases.
>
Probably it's my attempt to make it work with non-static libm that failed then,
is it supposed to work?
I see mention of BUILD_STATIC there, but it does not seem to actually work for me.
If I use static libm, then it works.
If I uninstall static libm, any attempt to build fails, regardless of whether I pass BUILD_STATIC='n' or so.
Ciao and thanks,
CLaudio
next prev parent reply other threads:[~2020-11-25 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 11:04 help with a build-user and build-user-plugin failure Claudio Fontana
2020-11-24 13:54 ` Philippe Mathieu-Daudé
2020-11-24 13:56 ` Claudio Fontana
2020-11-25 9:42 ` Alex Bennée
2020-11-25 12:00 ` Claudio Fontana [this message]
2020-11-25 17:02 ` Alex Bennée
2020-11-25 17:04 ` Claudio Fontana
2020-12-03 12:39 ` Claudio Fontana
2020-12-03 16:59 ` Alex Bennée
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=6efbff12-a10b-8e55-908b-f2233fc8001e@suse.de \
--to=cfontana@suse.de \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--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).