From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-05-21
Date: Fri, 22 May 2015 21:21:15 +0200 [thread overview]
Message-ID: <87d21s1kr8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150522172441.GB5153@free.fr> (Yann E. MORIN's message of "Fri, 22 May 2015 19:24:41 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Peter, Thomas, All,
> On 2015-05-22 09:20 +0200, Peter Korsgaard spake thusly:
>> > i686 | ipmiutil-2.9.5 | NOK |
>> > http://autobuild.buildroot.net/results/04a1c48d484debd7894fd32997ed50d3a0110b93/
>> > x86_64 | ipmiutil-2.9.5 | NOK |
>> > http://autobuild.buildroot.net/results/9accdfec87aa9922a4096b84a61a6e2dfd53561e/
>> Gaah, more ipmiutil issues. I believe Yann is looking into this.
> ipmiutil's Makefile.am-s are, let's say it politely, not the easiest to
> work with...
> So, regarding the parallel build issue, I'm bailing out. I am able to
> reproduce it in about 1 build out of ten, but then hacking Makefile.am
> is just of my league (they are ugly...).
Yeah. I don't have a problem with us using MAKE1 as it's a fairly small
package.
> Now, I'm looking at those new build failures. I suspect:
> 25e15fd package/ipmiutil: really force md2 off
> which introduced -DALLOW_GNU in the CFLAGS, and that has much mpre
> impact...
> Investigation in progress...
Thanks!
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2015-05-22 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-05-21 Thomas Petazzoni
2015-05-22 7:20 ` Peter Korsgaard
2015-05-22 7:56 ` Thomas Petazzoni
2015-05-22 17:24 ` Yann E. MORIN
2015-05-22 19:21 ` Peter Korsgaard [this message]
2015-05-23 16:25 ` Yann E. MORIN
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=87d21s1kr8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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