From: Warner Losh <imp@bsdimp.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Ed Maste <emaste@freebsd.org>,
QEMU Developers <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 08:05:43 -0700 [thread overview]
Message-ID: <CANCZdfqpRgAwsF1zE-25vhzEreB2erNOoU7d6DLAbJnx3etDQg@mail.gmail.com> (raw)
In-Reply-To: <87wnv4qq6v.fsf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Fri, Feb 19, 2021, 3:59 AM Alex Bennée <alex.bennee@linaro.org> wrote:
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > On Fri, 19 Feb 2021 at 10:39, Alex Bennée <alex.bennee@linaro.org>
> 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
> >
> > FWIW the vm-build-freebsd build-and-test works for me, as I
> > continue to run it as part of the merge tests. Is this something
> > to do with whether you already have a freebsd image cached
> > as opposed to it getting re-built from scratch (perhaps with
> > a newer FreeBSD)?
>
> It did re-run the installation when I first called the target so I guess
> it was that.
>
Python was built against a newer FreeBSD that had symbols that weren't in
12.1. Where did the python build come from?
Warner
--
> Alex Bennée
>
>
[-- Attachment #2: Type: text/html, Size: 2015 bytes --]
next prev parent reply other threads:[~2021-02-19 15:46 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 [this message]
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é
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=CANCZdfqpRgAwsF1zE-25vhzEreB2erNOoU7d6DLAbJnx3etDQg@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=gerd@kraxel.org \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@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).