From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: ARM unwind issue
Date: Mon, 28 Jan 2013 21:03:55 -0800 [thread overview]
Message-ID: <20130128210355.ca8cbd88.idunham@lavabit.com> (raw)
In-Reply-To: <CAPfzE3a0BaJmpx2tXD+2B57RHTFh6qHtCgKUSYxj1ERUx+qyeQ@mail.gmail.com>
On Tue, 29 Jan 2013 12:02:37 +1300
Andre Renaud <andre@bluewatersys.com> wrote:
> Hi,
> I'm trying to build some software using musl on an ARM platform, and
> am getting the following error:
> arm-none-linux-gnueabi-gcc
> -specs=/home/andre/work/package-builder/staging/lib/musl-gcc.specs -o
> program program.o
> /tools/arm/arm-2010q1/bin/../lib/gcc/arm-none-linux-gnueabi/4.4.1/../../../../arm-none-linux-gnueabi/bin/ld:
> program: hidden symbol `__aeabi_unwind_cpp_pr0' in
> /tools/arm/arm-2010q1/bin/../lib/gcc/arm-none-linux-gnueabi/4.4.1/libgcc_eh.a(unwind-arm.o)
> is referenced by DSO
A few details that might be informative:
1: I'm guessing that this is a prepackaged glibc-targetted x86->armel cross toolchain from Linaro, specifically their 2010 release?
2: I guess you're manually duplicating
REALGCC=/tools/arm/arm-2010q1/bin/gcc musl-gcc program.c -o program.o
3: Does this occur even with a trivial program (hello world or
int main(){ }) ?
> Any ideas on what I've messed up in either my musl build, or my
> cflags/lflags to cause this?
Googling "hidden symbol is referenced by DSO" I find that similar problems occurr with newlib when not linked with libgcc.
So it would probably help figure it out if you attached your config.mak and musl-gcc.specs.
> Regards,
> Andre
--
Isaac Dunham <idunham@lavabit.com>
next prev parent reply other threads:[~2013-01-29 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 23:02 Andre Renaud
2013-01-29 0:44 ` Rich Felker
2013-01-29 5:03 ` Isaac Dunham [this message]
2013-01-29 19:56 ` Andre Renaud
2013-01-29 23:55 ` Rich Felker
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=20130128210355.ca8cbd88.idunham@lavabit.com \
--to=idunham@lavabit.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).