All of 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 2014-05-11
Date: Fri, 16 May 2014 08:20:01 +0300	[thread overview]
Message-ID: <20140516052001.GQ4096@tarshish> (raw)
In-Reply-To: <637450823.253368.1400157851288.JavaMail.zimbra@advansee.com>

Hi Beno?t,

On Thu, May 15, 2014 at 02:44:11PM +0200, Beno?t Th?baudeau wrote:
> On Thursday, May 15, 2014 5:44:47 AM, Baruch Siach wrote:
> > On Thu, May 15, 2014 at 12:10:06AM +0200, Beno?t Th?baudeau wrote:
> > > Also, 'LSOF_INCLUDE="$(STAGING_DIR)/usr/include"' is explicitly asking
> > > the configuration script to mix native and cross stuff for tests.
> > 
> > This should be fixed then. I'll look into it.
> 
> Cool.

I went through the Configure script, and it seems that almost all uses of 
$LSOF_INCLUDE are for direct headers existence or grep tests, not build/run 
tests. I guess leaving the $LSOF_INCLUDE setting as is should be safe for now.

> OTOH, the worst test is probably the one for strftime() support, which
> just tests native toolchain features by running code on the build machine (not
> just testing #define-s).

This test doesn't use $LSOF_INCLUDE at all, and is a purely host test and thus 
useless. OTOH, there is no easy way to disable this test short of patching the 
Configure script. IMO this test is harmless. In case we encounter a target 
without strftime()/localtime(), we'll see a clear build failure. So I believe 
we should just leave this test as is for now as well.

> Most of the other tests do things like for GLIBC, hence
> a lot of mix-up in the header files.

Other that the glibc test which is now disabled I have not found any other 
example of host toolchain with target headers mix in the Configure script. 
Have you seen any?

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 -

  reply	other threads:[~2014-05-16  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-11 Thomas Petazzoni
2014-05-13  7:44 ` Thomas Petazzoni
2014-05-13  7:52   ` Baruch Siach
2014-05-13  8:01     ` Thomas Petazzoni
2014-05-14 20:56       ` Baruch Siach
2014-05-14 21:25         ` Benoît Thébaudeau
2014-05-15  7:50           ` Thomas Petazzoni
2014-05-15 12:51             ` Benoît Thébaudeau
     [not found]         ` <CA+sos78G3YxRUCd6pj8naGBSHANEp=1f5FrtuG2oeQpbhNbOuw@mail.gmail.com>
2014-05-14 21:41           ` Baruch Siach
2014-05-14 22:10             ` Benoît Thébaudeau
2014-05-15  3:44               ` Baruch Siach
2014-05-15 12:44                 ` Benoît Thébaudeau
2014-05-16  5:20                   ` Baruch Siach [this message]
2014-05-16 10:41                     ` Benoît Thébaudeau
2014-05-13  8:44   ` Peter Korsgaard
2014-05-13  8:57   ` Samuel Martin
2014-05-13  9:21   ` Gustavo Zacarias

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=20140516052001.GQ4096@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.