From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder site back online
Date: Mon, 18 Nov 2013 13:59:59 +0100 [thread overview]
Message-ID: <20131118135959.47faa95b@skate> (raw)
In-Reply-To: <528A0E38.9040905@mind.be>
Dear Arnout Vandecappelle,
On Mon, 18 Nov 2013 13:55:20 +0100, Arnout Vandecappelle wrote:
> I read:
>
> config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_14_3
> bool "Xilinx Little Endian Microblaze GNU Tools 14.3"
> depends on BR2_microblazeel
> depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
> depends on !BR2_PREFER_STATIC_LIB
>
> Is it possible that the autobuilder scripts randomly set
> BR2_PREFER_STATIC_LIB? If that is set, then none of the official
> external toolchain profiles work and the default will be a custom
> preinstalled one...
Aaah, you got it! Indeed the autobuilder randomly sets
BR2_PREFER_STATIC_LIB, and this isn't going to work properly when the
external toolchain is glibc based, since I've excluded glibc/eglibc
toolchains from the static build thing.
I guess I need to improve the autobuild script to only use
BR2_PREFER_STATIC_LIB when !glibc && !eglibc (i.e at the moment, when
uClibc is used).
Thanks for spotting this!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-18 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 21:36 [Buildroot] Autobuilder site back online Thomas Petazzoni
2013-11-17 8:03 ` Thomas De Schampheleire
2013-11-17 17:29 ` Yann E. MORIN
2013-11-17 17:50 ` Yann E. MORIN
2013-11-17 22:44 ` Thomas Petazzoni
2013-11-18 23:15 ` Arnout Vandecappelle
2013-11-18 23:30 ` Thomas Petazzoni
2013-11-20 11:45 ` Fatih Aşıcı
2013-11-20 12:30 ` Thomas Petazzoni
2013-11-17 17:58 ` Peter Korsgaard
2013-11-17 22:38 ` Thomas Petazzoni
2013-11-18 12:55 ` Arnout Vandecappelle
2013-11-18 12:59 ` Thomas Petazzoni [this message]
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=20131118135959.47faa95b@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox