Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Make problem on 64-bit linux with CS 2009q1
Date: Mon, 12 Dec 2011 20:43:20 +0100	[thread overview]
Message-ID: <87d3bttw2v.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAHUNapQTUqg5Vo4c57Yg4OqG+FL6trcjZBPJsEzfE0xGc=cdvQ@mail.gmail.com> (Trevor Woerner's message of "Mon, 12 Dec 2011 12:52:15 -0500")

>>>>> "Trevor" == Trevor Woerner <twoerner@gmail.com> writes:

Hi,

 Trevor> It appears that the contents of openSUSE 12.1's site file are buggy.

 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.


-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-12-12 19:43 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 [this message]
2011-12-14  7:08                     ` Arnout Vandecappelle
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=87d3bttw2v.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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