From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: update Linaro toolchains
Date: Mon, 10 Nov 2014 11:20:04 +0100 [thread overview]
Message-ID: <20141110112004.03adebb6@free-electrons.com> (raw)
In-Reply-To: <CAFbHwiSrjXBpYrVW+O3NqtZ+aToNaS=UQbeb_Do2n6ym0_6Sjg@mail.gmail.com>
Dear Will Newton,
On Mon, 10 Nov 2014 10:12:40 +0000, Will Newton wrote:
> > Bump the ARM, ARMeb and AArch64 Linaro toolchains from 14.08 to
> > 14.09. We can't bump to 14.10, because they completely changed the
> > toolchains and they are now completely broken: they switched from
> > Crosstool-NG to a new build tool to generate the toolchain, and now
> > the sysroot handling is completely borked.
>
> Do you have more details on this? If the new tool is causing problems
> for people then we need to address those.
Yes, I first complained on my G+ (I know, it's silly):
https://plus.google.com/101327154101389327284/posts/SjFkrX3ow5M. And
I'm going to fill a bug to the Linaro bug tracker, I just created an
account today.
Basically, the sysroot handling is not done correctly, so the toolchain
is not relocatable: -print-sysroot and -print-file-name=libc.a return
invalid values.
Just have a look at the INSTALL-sysroot.sh script inside the toolchain,
it gives you an idea on how bad the toolchain is.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-10 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 10:06 [Buildroot] [PATCH] toolchain-external: update Linaro toolchains Thomas Petazzoni
2014-11-10 10:12 ` Will Newton
2014-11-10 10:20 ` Thomas Petazzoni [this message]
2014-11-10 10:33 ` Will Newton
2014-11-11 20:32 ` Peter Korsgaard
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=20141110112004.03adebb6@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.