From: Ed Maste <emaste@freebsd.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hosted CI for FreeBSD - Cirrus CI
Date: Tue, 15 Jan 2019 13:58:05 -0500 [thread overview]
Message-ID: <CAPyFy2AJR93Sk65UnB52u1Wz_T-mzzdMcs9b1HDFdb4cRsz+_A@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-VWHgcfmKTfjTGGQXKTp8V5thsFO0tJ6R-p+MQHkcm1g@mail.gmail.com>
On Tue, 15 Jan 2019 at 13:47, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > It looks like this was introduced between
> > 9b2e891ec5ccdb4a7d583b77988848282606fdea (works) and
> > 44ba6010635641a538c9b9b1f377dfa288751906 (fails). The .cirrus.yml file
> > in my branch is at least good enough to catch this sort of thing, so
> > I'll send the patch over (while trying to look into this).
>
> Commit fea35ca4b8e68b4fa updates our configure test to require
> a libfdt version that has fdt_check_full() in it, so in theory
> what is supposed to happen is that we will use the local
> version in dtc/ if the system libfdt is not new enough.
> Has that process gone wrong? Is the build using the system
> libfdt or the one we provide in the submodule ?
>From the log[1] it looks like it's building the libfdt from dtc/.
Unfortunately I'm unable to dig in deeper into the hosted build (I
have only the logs), and my local build attempts are currently failing
due to unrelated issues. I'll investigate further as soon as I can.
[1] https://cirrus-ci.com/task/6254685977575424
next prev parent reply other threads:[~2019-01-15 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 20:43 [Qemu-devel] Hosted CI for FreeBSD - Cirrus CI Ed Maste
2018-12-05 21:01 ` Kamil Rytarowski
2018-12-05 21:58 ` Ed Maste
2018-12-06 1:08 ` Kamil Rytarowski
2018-12-06 10:23 ` Daniel P. Berrangé
2018-12-06 18:25 ` Ed Maste
2018-12-07 9:54 ` Daniel P. Berrangé
2018-12-14 14:57 ` Ed Maste
2019-01-15 18:32 ` Ed Maste
2019-01-15 18:47 ` Peter Maydell
2019-01-15 18:58 ` Ed Maste [this message]
2019-01-15 21:23 ` Ed Maste
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=CAPyFy2AJR93Sk65UnB52u1Wz_T-mzzdMcs9b1HDFdb4cRsz+_A@mail.gmail.com \
--to=emaste@freebsd.org \
--cc=berrange@redhat.com \
--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).