From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] icu: detect and add compiler symbol prefix to the assembly code
Date: Thu, 20 Feb 2014 08:31:02 +0100 [thread overview]
Message-ID: <20140220083102.609c5783@skate> (raw)
In-Reply-To: <87wqgqyaxy.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 19 Feb 2014 23:50:01 +0100, Peter Korsgaard wrote:
> We recently added this patch to icu for bfin symbol prefix, but from
> todays autobuilder I see that icu's configure script completely doesn't
> support uclinux (E.G. bfin):
>
> http://autobuild.buildroot.net/results/d11/d118b4f753ade63201758e1b14ca54d96ec77698/build-end.log
>
> What's going on here? Should I revert this patch and instead mark icu as
> unavailable on bfin?
No. I believe icu support bfin-linux-uclibc (i.e FDPIC), but not
bfin-uclinux. I've modified icu so that it accepts bfin-uclinux as
well, but apparently icu generates an ELF file by itself (!), and puts
it in an .a archive. Which of course is not really to the taste of the
FLAT format ld used on bfin-uclinux.
I'm trying to figure out if icu can be convinced to generate source
code instead and compile it, but the icu source code is weird, to say
the least.
So I believe I will send a patch that disables ICU when !BR2_BINFMT_ELF.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-20 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 13:06 [Buildroot] [PATCH v2 1/1] icu: detect and add compiler symbol prefix to the assembly code Ryan Barnett
2014-02-04 13:40 ` Thomas Petazzoni
2014-02-04 14:10 ` Ryan Barnett
2014-02-04 14:28 ` Peter Korsgaard
2014-02-04 14:28 ` Peter Korsgaard
2014-02-19 22:50 ` Peter Korsgaard
2014-02-20 7:31 ` Thomas Petazzoni [this message]
2014-02-20 7:49 ` 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=20140220083102.609c5783@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 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.