Re: [Gcl-devel] Unrelocated symbol: __aeabi_unwind_cpp_pr1

[Camm Maguire]

Greetings!

1) So I take it you also tried Will Newton's shared-libgcc to no avail?
2) Do you know why this arm is different from Debian's armel and armhf?
3) Do you know what the symbols do, or what compiled code pulls them in?
4) Is this specific to some Fedora gcc compile flag?

I guess this work around is as good as any for now, but I've been trying
to get away from use_symbols -- fragile and ugly.

Take care,

Jerry James <address@hidden> writes:

> On Tue, Sep 9, 2014 at 1:36 PM, Jerry James <address@hidden> wrote:
>> Oh, wait!  I didn't notice that the previous recipe (calling the
>> function from use_symbols) *worked*, and it is now complaining about
>> __aeabi_unwind_cpp_pr0.  That is, it's a different symbol, ending with
>> a zero instead of a 1 now.  Sorry about that.  Okay, I will now add a
>> call to __aeabi_unwind_cpp_pr0 as well and we'll see if it wants
>> anything else.
>
> I don't know why the TLDFLAGS and TLIBS approaches did not work, but
> this patch led to a successful build:
>
> --- o/sfasli.c.orig 2014-09-06 09:45:30.000000000 -0600
> +++ o/sfasli.c 2014-09-09 12:00:00.000000000 -0600
> @@ -133,6 +133,11 @@ extern int __remqu();
>
>  #ifndef DARWIN
>  #ifndef _WIN32
> +#if defined(__arm__) && !defined(__aarch64__)
> +extern void __aeabi_unwind_cpp_pr0(void);
> +extern void __aeabi_unwind_cpp_pr1(void);
> +#endif
> +
>  int
>  use_symbols(double d,...) {
>
> @@ -141,6 +146,10 @@ use_symbols(double d,...) {
>  #ifdef GCL_GPROF
>    _mcount();
>  #endif
> +#if defined(__arm__) && !defined(__aarch64__)
> +  __aeabi_unwind_cpp_pr0();
> +  __aeabi_unwind_cpp_pr1();
> +#endif
>
>    return (int)d;
>
> Now to try building on aarch64 and see what happens.

-- 
Camm Maguire                                        address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah