From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core: fix setting of HOSTARCH
Date: Thu, 12 Nov 2015 09:28:20 +0100 [thread overview]
Message-ID: <20151112092820.4500de49@free-electrons.com> (raw)
In-Reply-To: <87si4bocvr.fsf@dell.be.48ers.dk>
Hello,
On Thu, 12 Nov 2015 09:11:52 +0100, Peter Korsgaard wrote:
> > Those build failures are not caused by a 32 bits vs. 64 bits issue. In
> > fact, I started running my chroot under "linux32", but it was even
> > worse. Because indeed my chroots *are* 64 bits.
>
> > However, the real problem is that the new Linaro toolchains have been
> > built against glibc 2.14 (for the host), while my chroot only uses
> > glibc 2.11 (from Debian 6.0).
>
> Ahh. Debian 6.0 is getting quite old (2011), but yeah - People on
> Enterprise distributions might end up with the same problems.
Indeed, and that's why I'd like to keep my old distro.
> > I'm not sure how to handle this. Some old distros may not have glibc
> > 2.14.
>
> I don't think there's much we can do, besides perhaps adding a comment
> in the help text.
>
> I'm not sure how realistic it is to convince the Linaro people to build
> their toolchains on ancient distributions.
So I guess that the only reasonable option here is that I had some
logic in autobuild-run to not use this toolchain when the host C
library is too old. This way, we keep using the Linaro toolchain on
build slaves that are modern enough, and we don't have build failures
on the others.
Thoughts?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-12 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:00 [Buildroot] [PATCH] core: fix setting of HOSTARCH Yann E. MORIN
2015-11-09 22:01 ` Arnout Vandecappelle
2015-11-09 22:17 ` Yann E. MORIN
2015-11-10 21:48 ` Arnout Vandecappelle
2015-11-11 22:53 ` Thomas Petazzoni
2015-11-11 22:58 ` Yann E. MORIN
2015-11-12 7:52 ` Peter Korsgaard
2015-11-12 17:35 ` Yann E. MORIN
2015-11-12 8:11 ` Peter Korsgaard
2015-11-12 8:28 ` Thomas Petazzoni [this message]
2015-11-12 8:49 ` Peter Korsgaard
2016-01-19 23:11 ` 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=20151112092820.4500de49@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.