From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder news
Date: Sun, 04 May 2014 23:32:12 +0200 [thread overview]
Message-ID: <5366B1DC.4020604@lucaceresoli.net> (raw)
In-Reply-To: <20140504223611.5a6177c1@skate>
Hi Thomas, Yann, Arnout, all,
Thomas Petazzoni wrote:
> Hello,
>
> Two news about the autobuilders:
>
> * The Crosstool-NG external toolchain configurations have been updated
> and slightly extended. Yann E. Morin has provided me with a good set
> of more up-to-date toolchains generated by Crosstool-NG, and I've
> added them to the Free Electrons autobuilders, as a replacement for
> the old ones. The new configurations are:
>
> http://autobuild.buildroot.org/toolchains/configs/free-electrons/armv5-ctng-linux-gnueabi.config
> http://autobuild.buildroot.org/toolchains/configs/free-electrons/armv6-ctng-linux-uclibcgnueabi.config
> http://autobuild.buildroot.org/toolchains/configs/free-electrons/armv7-ctng-linux-gnueabihf.config
With reference to the discussion I started a couple of weeks ago [1],
there is now a non-Linaro external EABIhf toolchain on the autobuilders.
I checked it and it does not seem to produce the same problem I met,
because it ships ld-linux-armhf.so.3, not ld-linux.so.3, but I don't
think it is a multilib toolchain, is it?
Is it a habit in modern EABIhf toolchains to name the dynamic linker
ld-linux-armhf instead of ld-linux. This would explain why I have a
problem that nobody else seems to have here.
[1]
http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/82456/focus=82471
--
Luca
next prev parent reply other threads:[~2014-05-04 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 20:36 [Buildroot] Autobuilder news Thomas Petazzoni
2014-05-04 21:32 ` Luca Ceresoli [this message]
2014-05-10 20:28 ` Arnout Vandecappelle
2014-05-11 16:07 ` Thomas Petazzoni
2014-05-11 16:29 ` Thomas Petazzoni
2014-05-11 20:37 ` Arnout Vandecappelle
2014-05-11 21:14 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2014-08-29 21:26 Thomas Petazzoni
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=5366B1DC.4020604@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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.