From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-09
Date: Wed, 11 Dec 2013 09:16:44 +0200 [thread overview]
Message-ID: <20131211071643.GF1217@tarshish> (raw)
In-Reply-To: <ad79e2e1-bce2-4354-8b64-7b2bc5082d0e@email.android.com>
Hi Thomas,
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.
baruch
--
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 -
next prev parent reply other threads:[~2013-12-11 7:16 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 [this message]
2013-12-19 10:22 ` Baruch Siach
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=20131211071643.GF1217@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 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.