From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Make problem on 64-bit linux with CS 2009q1
Date: Wed, 14 Dec 2011 08:08:49 +0100 [thread overview]
Message-ID: <201112140808.49826.arnout@mind.be> (raw)
In-Reply-To: <87d3bttw2v.fsf@macbook.be.48ers.dk>
On Monday 12 December 2011 20:43:20 Peter Korsgaard wrote:
> Trevor> The CONFIG_SITE mechanism is purposefully provided to help "prime the
> Trevor> cache" for ./configure scripts when cross compiling to provide answers
> Trevor> to questions which would normally require code to be compiled and run
> Trevor> (which fails, of course, when the compiler being used is a cross
> Trevor> compiler).
>
> Trevor> Should the CONFIG_SITE feature be disabled and otherwise unavailable
> Trevor> to users just because there's a bug in openSUSE's implementation?
>
> Yes, because whatever defaults potentially could make sense for the
> build host in general doesn't make sense for the target, and for BR
> builds to reproducable behaviour shouldn't change depending on something
> outside our control.
>
> You could perhaps argue for allowing it for host packages, but the
> simplest/safest option is just to disallow it for all.
Or better yet, to use our own and prime it with all the generic configure
variables. That may bring down the huge amount of time spent in running
configure scripts...
OTOH, if the one that SUSE provides is buggy, that is probably because it
is difficult to get it correct...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-12-14 7:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 8:47 [Buildroot] Make problem on 64-bit linux with CS 2009q1 Guillaume Gardet
2011-12-09 18:37 ` Thomas Petazzoni
2011-12-09 21:40 ` Peter Korsgaard
2011-12-09 22:45 ` Peter Korsgaard
2011-12-09 23:27 ` Trevor Woerner
2011-12-10 10:06 ` Guillaume Gardet
2011-12-10 19:27 ` Peter Korsgaard
2011-12-12 8:23 ` Guillaume Gardet
2011-12-12 9:15 ` Peter Korsgaard
2011-12-12 10:13 ` Guillaume Gardet
2011-12-12 10:17 ` Thomas Petazzoni
2011-12-12 10:26 ` Guillaume Gardet
2011-12-12 17:52 ` Trevor Woerner
2011-12-12 19:43 ` Peter Korsgaard
2011-12-14 7:08 ` Arnout Vandecappelle [this message]
2011-12-14 8:31 ` Thomas Petazzoni
2011-12-14 8:41 ` Peter Korsgaard
2011-12-14 8:42 ` Peter Korsgaard
2011-12-12 10:35 ` Peter Korsgaard
2011-12-12 10:42 ` Guillaume Gardet
2011-12-12 12:19 ` Trevor Woerner
2011-12-10 10:01 ` Guillaume Gardet
2011-12-10 19:28 ` Peter Korsgaard
2011-12-12 8:25 ` Guillaume Gardet
2011-12-10 10:28 ` Guillaume Gardet
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=201112140808.49826.arnout@mind.be \
--to=arnout@mind.be \
--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