Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] BuildRoot cannot build powerpc64
Date: Wed, 24 Aug 2016 11:37:04 +0200	[thread overview]
Message-ID: <878tvmh5j3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1b65f937-d2ee-312c-964d-e6b9da957463@mind.be> (Arnout Vandecappelle's message of "Wed, 24 Aug 2016 03:01:00 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >>> Actually also some other options are more fitting in the toolchain menu IMHO,
 >>> like debug/optimization options and SSP.
 >> 
 >> I personally don't like this, and instead would like to keep separated
 >> the options that affect the build of all components (SSP or not,
 >> debug/optimization, shared/static) from the options that configure the
 >> toolchain itself.

 >  OK, fair enough.

 >  Actually, I noticed now that SSP in the build menu already depends on the
 > toolchain choices. So perhaps we should move the build options below the
 > toolchain, and make the static/shared libs options depend on the toolchain as well.

Yes, perhaps that is less confusing. It isn't perfect as the build
options are more general than toolchain, but the current setup where
people have to jump back/forth between the build options and toolchain
menus also isn't very nice.

 >  That leaves us just with the awkward headers-same-as-kernel forward dependency.

Yeah :/

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2016-08-24  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 22:43 [Buildroot] BuildRoot cannot build powerpc64 ANDY KENNEDY
2016-08-17  0:24 ` Ricardo Martincoski
2016-08-17 15:33   ` ANDY KENNEDY
2016-08-17 17:37     ` Thomas Petazzoni
2016-08-17 19:00       ` Waldemar Brodkorb
2016-08-18 18:02       ` Arnout Vandecappelle
2016-08-18 21:18         ` Thomas Petazzoni
2016-08-24  1:01           ` Arnout Vandecappelle
2016-08-24  9:37             ` Peter Korsgaard [this message]
2016-08-18 21:19         ` Khem Raj

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=878tvmh5j3.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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