Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPfzE3Zzexi8n534g-pCwoKUdcKvJ9KbQ6QEquhQdYZMTgkdtQ@mail.gmail.com>
Date: Wed, 30 Jan 2013 08:56:27 +1300
From: Andre Renaud <andre@...ewatersys.com>
To: musl@...ts.openwall.com
Subject: Re: ARM unwind issue

>> 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?

It's the codesourcery 2010q1 release.

> 2: I guess you're manually duplicating
> REALGCC=/tools/arm/arm-2010q1/bin/gcc musl-gcc program.c -o program.o
I actually wasn't using musl-gcc, I was manually adding the '-spec' line.

It turns out that the root cause was a mistake on my behalf when
configuring musl, which resulted in LIBCC not being set properly in
config.mak.

Regards,
Andre

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.