From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] PowerPC64 toolchain not building
Date: Thu, 28 Jan 2016 09:17:42 +0100 [thread overview]
Message-ID: <20160128091742.45cad80d@free-electrons.com> (raw)
In-Reply-To: <20160128024442.GA5589@tungsten.ozlabs.ibm.com>
Hello,
On Thu, 28 Jan 2016 13:44:42 +1100, Sam Bobroff wrote:
> > You need to select the power8 processor for the issue to reproduce. It
> > doesn't appear with power7 for example.
>
> Hmm, while that's not surprising, I've used that combination of options (power8
> big-endian with gcc 4.9.x and gcc 5.x) and it works fine for me. Have you tried
> building from completely clean, including clearing or disabling ccache?
Yes, I'm doing completely clean builds, I never use ccache, and always
start my builds from scratch.
Waldemar, are you able to reproduce the build failure on Power8 ?
> Maybe the host architecture matters? Is that x86_64? What gcc do you have on
> the host?
Yes, x86_64, the host gcc is quite old (4.4) since I'm using Debian 6.0
on this build server instance.
I've restarted a build on my laptop, which has a more modern distro,
I'll let you know the results.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-28 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:07 [Buildroot] PowerPC64 toolchain not building Thomas Petazzoni
2016-01-24 19:12 ` Waldemar Brodkorb
2016-01-24 20:36 ` Thomas Petazzoni
2016-01-27 4:38 ` Sam Bobroff
2016-01-27 8:32 ` Thomas Petazzoni
2016-01-28 2:44 ` Sam Bobroff
2016-01-28 8:17 ` Thomas Petazzoni [this message]
2016-01-28 9:20 ` Thomas Petazzoni
2016-01-29 0:55 ` Sam Bobroff
2016-02-03 14:45 ` Thomas Petazzoni
2016-01-28 9:47 ` Waldemar Brodkorb
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=20160128091742.45cad80d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.