Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-09
Date: Thu, 19 Dec 2013 12:22:20 +0200	[thread overview]
Message-ID: <20131219102220.GD4148@tarshish> (raw)
In-Reply-To: <20131211071643.GF1217@tarshish>

Hi Thomas,

On Wed, Dec 11, 2013 at 09:16:44AM +0200, Baruch Siach wrote:
> On Wed, Dec 11, 2013 at 07:28:35AM +0100, Thomas De Schampheleire wrote:
> > Baruch Siach <baruch@tkos.co.il> wrote:
> > >On Tue, Dec 10, 2013 at 08:30:07AM +0100, Thomas Petazzoni wrote:
> > >>     xtensa |                      m4-1.4.17 | NOK | http://autobuild.buildroot.net/results/0b9b3bb1791bbc9f902a23360c4540d90a0e05ca/
> > >>     xtensa |                      m4-1.4.17 | NOK | http://autobuild.buildroot.net/results/ffda6f3f64c612da999229226f699c01ccebe4c2/
> > >
> > >I'm struggling with this one. The configure script test for posix_spawn build 
> > >fails because it lacks '-lrt'. This causes m4 to use an internal 
> > >implementation that fails at build time for some other reason (haven't found 
> > >the reason for that yet).
> > >
> > >How can I add -lrt to the build test command line?
> > 
> > Isn't this by adding/setting the LIBS variable before
> > calling the macro that executes the test? 
> 
> Thanks, I'll try that. This macro seems to be called from m4/spawn_h.m4. This 
> failures seems to be xtensa specific. I wonder how other archs handle this.

Well, this check seems to come from gnulib. How can I fix it then?

BTW, coreutils shows the same problem 
(http://autobuild.buildroot.net/results/514/5147d4962bf486c91c314eda4894140f31ea1b44/).

I still don't understand why the autobuilder doesn't fail on other archs. I 
can reproduce this failure on ARM with the following defconfig:

BR2_arm=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PACKAGE_M4=y

Thomas P, is there a way to see the config.log file from a successful build of 
m4 on the autobuilder?

These successes are quite hard to find, it seems. Of the latest 50 autobuilds, 
the m4 package is selected in only 3 configs with the following results:

Same failure on arc
http://autobuild.buildroot.net/results/ebf/ebf731271dc74d8b17304df3de8eb34220ce371e/

Failure for other reason on x86_64
http://autobuild.buildroot.net/results/dbd/dbd7030f9a04d6aaf19b60ae04a2359228dda926/

Success on sh4a, apparently using glibc newer than 2.16 that moved posix_spawn 
into the main libc.so
http://autobuild.buildroot.net/results/0a2/0a29c9c8cc268a2d2468c6d2bccf27a77caefebf/

baurch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2013-12-19 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-09 Thomas Petazzoni
2013-12-11  4:38 ` Baruch Siach
2013-12-11  6:28   ` Thomas De Schampheleire
2013-12-11  7:16     ` Baruch Siach
2013-12-19 10:22       ` Baruch Siach [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=20131219102220.GD4148@tarshish \
    --to=baruch@tkos.co.il \
    --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