From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Ed Maste <emaste@freebsd.org>,
qemu-devel@nongnu.org, Gerd Hoffmann <gerd@kraxel.org>,
Li-Wen Hsu <lwhsu@freebsd.org>
Subject: Re: FreeBSD build regressions
Date: Fri, 19 Feb 2021 10:42:58 +0000 [thread overview]
Message-ID: <YC+WMtkuQjttKns9@redhat.com> (raw)
In-Reply-To: <8735xss5q3.fsf@linaro.org>
On Fri, Feb 19, 2021 at 10:29:50AM +0000, Alex Bennée wrote:
>
> Hi,
>
> It looks like the build has been broken on Cirrus since at least 7b2c4c:
>
> https://cirrus-ci.com/github/qemu/qemu
>
> I did attempt to have a look but "vm-build-freebsd" seems to be failing
> with a different error:
>
> 10:31:47 [alex.bennee@hackbox2:~/l/q/b/all] master|✔ + make vm-build-freebsd
> GIT ui/keycodemapdb tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3 meson dtc capstone slirp
> VM-BUILD freebsd
> cross containers no
>
> NOTE: guest cross-compilers enabled: cc cc
> ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6"
> ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6"
> The Meson build system
> Version: 0.55.3
> Source dir: /usr/home/qemu/qemu-test.egp8wG/src
> Build dir: /usr/home/qemu/qemu-test.egp8wG/build
> Build type: native build
> Project name: qemu
> Project version: 5.2.50
> ld-elf.so.1: /usr/local/lib/libpython3.7m.so.1.0: Undefined symbol "close_range@FBSD_1.6"
>
> ../src/meson.build:1:0: ERROR: Executables created by c compiler cc are not runnable.
>
> A full log can be found at /usr/home/qemu/qemu-test.egp8wG/build/meson-logs/meson-log.txt
>
> ERROR: meson setup failed
>
> /home/alex.bennee/lsrc/qemu.git/tests/vm/Makefile.include:95: recipe for target 'vm-build-freebsd' failed
> make: *** [vm-build-freebsd] Error 3
>
> Tracking back to before the previously mentioned commit it was still
> failing which makes me think something has happened to the BSD image (or
> something is missing since the build changes). I'd appreciate it if
> someone with more FreeBSD knowledge can look into both regressions
> because frankly I find it exhausting enough tracking down Linux
> regressions when they occur.
Yes, this is a problem with the image in Cirrus, which hit libvirt
CI too. We "fixed" it by changing to the freebsd-12-2 instead of
freebsd-12-1 image.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2021-02-19 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 10:29 FreeBSD build regressions Alex Bennée
2021-02-19 10:41 ` Peter Maydell
2021-02-19 10:58 ` Alex Bennée
2021-02-19 15:05 ` Warner Losh
2021-02-19 15:24 ` Gerd Hoffmann
2021-02-19 16:08 ` Warner Losh
2021-02-19 16:13 ` Peter Maydell
2021-02-19 18:28 ` Warner Losh
2021-02-19 10:42 ` Daniel P. Berrangé [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=YC+WMtkuQjttKns9@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=gerd@kraxel.org \
--cc=lwhsu@freebsd.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).