From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] Recurrent Blackfin build failure on icu
Date: Thu, 20 Jun 2013 19:21:48 -0400 [thread overview]
Message-ID: <201306201921.49209.vapier@gentoo.org> (raw)
In-Reply-To: <CAJxxZ0NqXVjrO9_d6mYALXP6ktvLMxXFyc--RS9y9GVm5UkE7Q@mail.gmail.com>
On Wednesday 05 June 2013 22:32:27 Sonic Zhang wrote:
> On Mon, Jun 3, 2013 at 5:38 PM, Thomas Petazzoni wrote:
> > 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?
>
> Maybe you can check the symbol name after compiling a C file into an
> assembly file?
gcc provides __USER_LABEL_PREFIX__ specifically for this. but you'd have to
create a .S file and run it through the preprocessor to do that ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130620/c44662b3/attachment.asc>
next prev parent reply other threads:[~2013-06-20 23:21 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
2013-06-06 2:32 ` Sonic Zhang
2013-06-06 6:07 ` Thomas Petazzoni
2013-06-20 23:21 ` Mike Frysinger [this message]
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=201306201921.49209.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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