From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-09-14
Date: Tue, 18 Sep 2018 09:28:29 +0200 [thread overview]
Message-ID: <20180918092829.721f3c54@windsurf> (raw)
In-Reply-To: <CALURroTZCjCkEw5-CjQDLju74tZqO2nkcPuT0KwG0UVq7YBEAA@mail.gmail.com>
Hello,
Adding Buildroot mailing list in Cc.
On Mon, 17 Sep 2018 08:57:06 -0700, Christopher McCrory wrote:
> > arc | perl-data-uuid-1.221 |
> > http://autobuild.buildroot.net/results/c5ba7b0727131220b60a4dc78fc7491dd4f7af9e
> > aarch64 | perl-data-uuid-1.221 |
> > http://autobuild.buildroot.net/results/5dd93ef9f5146227b8233ada260d5945aa8632d0
> > x86_64 | perl-io-socket-multicast-1.12 |
> > http://autobuild.buildroot.net/results/824119c86a1ddcbad39d4d4e9fe61eba20a55f3f
>
> I did a build with one of these configs and couldn't reproduce the error.
> IIRC, There was a patch to perl to fix these. yes?
>
Yes, these issues were fixed by
https://git.buildroot.org/buildroot/commit/package/pkg-perl.mk?id=45076af4930fda83c8898254de2d7c5fe3c15911
If you see any of those issues after commit
45076af4930fda83c8898254de2d7c5fe3c15911, then we have a separate
problem that needs to be investigated.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2018-09-18 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180915060039.36CDD207B0@mail.bootlin.com>
[not found] ` <CALURroTZCjCkEw5-CjQDLju74tZqO2nkcPuT0KwG0UVq7YBEAA@mail.gmail.com>
2018-09-18 7:28 ` Thomas Petazzoni [this message]
[not found] <20180915060039.533E3207D4@mail.bootlin.com>
[not found] ` <CAGrGpJDdVmD6PkhrZJgpTJut7vdvbxhS0m5Tg2DXPJZS90Vv6g@mail.gmail.com>
2018-10-06 7:39 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-09-14 Thomas Petazzoni
2018-10-06 22:26 ` Peter Thompson
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=20180918092829.721f3c54@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.