From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-31
Date: Sun, 1 Apr 2018 18:34:24 +0100 [thread overview]
Message-ID: <20180401183424.GD18124@momiji> (raw)
In-Reply-To: <20180401150727.GB18124@momiji>
On Sun, 1 Apr 2018 15:07:27 +0100, Adrian Perez de Castro <aperez@igalia.com> wrote:
> Hi,
>
> On Sun, 1 Apr 2018 08:00:18 +0200 (CEST), Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>
> > arm | brotli-1.0.3 | NOK | http://autobuild.buildroot.net/results/c2d7ef28b3af3b680ba62a5557ecf5b1f3915ad3 |
> > arm | brotli-1.0.3 | NOK | http://autobuild.buildroot.net/results/ca2a9770f64a10fd1b54ecdd08d292dfd67d7918 |
> > m68k | brotli-1.0.3 | NOK | http://autobuild.buildroot.net/results/0215539bf726532b464e2a527140b6a06dd0091d |
>
> The two failures in ARM should be fixed by this recent commit:
>
> https://git.busybox.net/buildroot/commit/?id=557cd845b216de8bfe7bb8d2ebf61bf020026f90
>
> I suspect that the build failure on m68k might be fixed by this one as well,
> right now I'm running a local build with that configuration to check.
My local build for m68k completed successfully, so it seems the patch for
fixing the static build of brotli also works for the m68k failure :-)
Cheers,
--
Adri?n ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180401/eceeda52/attachment.asc>
prev parent reply other threads:[~2018-04-01 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-31 Thomas Petazzoni
2018-04-01 14:07 ` Adrian Perez de Castro
2018-04-01 17:34 ` Adrian Perez de Castro [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=20180401183424.GD18124@momiji \
--to=aperez@igalia.com \
--cc=buildroot@busybox.net \
/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