From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] BuildRoot cannot build powerpc64
Date: Wed, 17 Aug 2016 21:00:47 +0200 [thread overview]
Message-ID: <20160817190047.GG22524@waldemar-brodkorb.de> (raw)
In-Reply-To: <20160817193721.0cc1466d@free-electrons.com>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Wed, 17 Aug 2016 15:33:30 +0000, ANDY KENNEDY wrote:
>
> > Our RFS we like to have static, so that we can throw libs into
> > the system @ runtime without breaking our stable RFS.
> >
> > Based upon your e-mail, I dropped into the uclibc dependencies
> > || BR2_powerpc64, which made it selectable. Problem is that
> > it wouldn?t build. My guess is that the T-series parts haven't
> > been added to uClibC-ng yet, which is why it isn't selectable.
> >
> > Thus, the answer to my question is "it is by design".
>
> 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.
Latest musl release supports ppc64.
I will sent a patch to allow to build it.
best regards
Waldemar
next prev parent reply other threads:[~2016-08-17 19:00 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 [this message]
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
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=20160817190047.GG22524@waldemar-brodkorb.de \
--to=wbx@openadk.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