From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BuildRoot cannot build powerpc64
Date: Thu, 18 Aug 2016 23:18:50 +0200 [thread overview]
Message-ID: <20160818231850.4072ddf2@free-electrons.com> (raw)
In-Reply-To: <532ce6e0-de27-9a2a-f062-179a4fa3248e@mind.be>
Hello,
On Thu, 18 Aug 2016 20:02:31 +0200, Arnout Vandecappelle wrote:
> > The only C library that supports PowerPC64 today is glibc.
> >
> > But glibc does not support static linking.
> >
> > Hence there is no solution to do a statically linked rootfs on
> > PowerPC64 today.
>
> Perhaps we should remove the static/shared libs options to the toolchain menu,
> and make them depend on the libc choice rather than the other way round. That
> way, we're sure that we never run into such impossible situations.
>
> 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.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-18 21:18 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 [this message]
2016-08-24 1:01 ` Arnout Vandecappelle
2016-08-24 9:37 ` Peter Korsgaard
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=20160818231850.4072ddf2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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