From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Recurrent Blackfin build failure on icu
Date: Mon, 3 Jun 2013 11:38:57 +0200 [thread overview]
Message-ID: <20130603113857.0c7ff74a@skate> (raw)
In-Reply-To: <CAJxxZ0MzWeQ4USQbwNwAuxGpkvwcejqaZvC7bGpySrZCdzus+g@mail.gmail.com>
Dear Sonic Zhang,
On Mon, 3 Jun 2013 17:26:08 +0800, Sonic Zhang wrote:
> For historic reasons, Blackfin GNU toolchain generate assembly symbols
> with the prefix '_'. For example: _uconvmsg_dat and _icudt48_dat .
> But, the pkgdata tool in icu doesn't generate assembly file
> uconvmsg_dat.s and icudt48l_dat.s in this way when Blackfin GNU
> toolchain is used. What do you think is a better way to fix it?
Can this specific behavior of the Blackfin toolchain be detected? Is
there a typical autotools test that would allow to test this?
Adding Mike in Cc, since I'm pretty sure he has some ideas about this.
> /buildroot/output/build/host-icu-4.8.1.1/source/bin/pkgdata -p
> uconvmsg -O pkgdata.inc -m static -s uconvmsg -d uconvmsg -T uconvmsg
> uconvmsg/uconvmsg.lst
>
>
> .globl uconvmsg_dat
> .section .note.GNU-stack,"",%progbits
> .section .rodata
> .align 8
> .type uconvmsg_dat,%object
> uconvmsg_dat:
> ...
>
>
> In addition, I am fine to receive the test log by this email.
Ok, I'll work on this.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-03 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 19:35 [Buildroot] Recurrent Blackfin build failure on icu Thomas Petazzoni
2013-06-03 9:26 ` Sonic Zhang
2013-06-03 9:38 ` Thomas Petazzoni [this message]
2013-06-06 2:32 ` Sonic Zhang
2013-06-06 6:07 ` Thomas Petazzoni
2013-06-20 23:21 ` Mike Frysinger
2013-06-21 6:38 ` 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=20130603113857.0c7ff74a@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