This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
- From: Andrew Haley <aph at redhat dot com>
- To: Cyd Haselton <chaselton at gmail dot com>, brian at shapes dot demon dot co dot uk
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Wed, 07 Jan 2015 17:40:35 +0000
- Subject: Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
- Authentication-results: sourceware.org; auth=none
- References: <CAHu5PrboyVq7orESm4N3m+2aQZaQNPAkcG4AJ7rFnFu+Q=tKWQ at mail dot gmail dot com> <CAHu5PrZ2-Ts7SOqtj=ZdyFbAWpYhf5uEqMAieuJx+1SpmvV1rQ at mail dot gmail dot com> <54A660C4 dot 3030108 at redhat dot com> <CAHu5PrbjFyy83xYUdx+vSVQuVJhD-_HzEAb735o_K+dVbXDLag at mail dot gmail dot com> <54A67520 dot 6030801 at redhat dot com> <CAHu5PrZpsNYawNMacyuZMb9owEsRFf8NN6KqsZZ-zbxYf8_JrA at mail dot gmail dot com> <CAHu5PrY3WjeVGb6e_pgKuALw+kdkJ5HaOSTpAAZpPA3g0i9CNA at mail dot gmail dot com> <1420567682 dot 2034 dot 9 dot camel at shapes dot demon dot co dot uk> <54AC3540 dot 30100 at redhat dot com> <CAHu5PrYEnSjZiu6QSb=75AueOSyqu7jwxeEJW5UaAw+zQ2F51Q at mail dot gmail dot com> <54AD0516 dot 5000804 at redhat dot com> <54AD23EA dot 2070905 at redhat dot com> <1420636833 dot 1716 dot 2 dot camel at shapes dot demon dot co dot uk> <54AD369D dot 1020208 at redhat dot com> <CAH6eHdQHSz7Jih1a=cYLLURM=TQdhragb9D6Jj+CsDF_nb4RQQ at mail dot gmail dot com> <CAHu5PrZ4sFL60eAk=S7G2kENv8! -gfAVYn+fkum97FK+Co4wOzA at mail dot gmail dot com> <1420643266 dot 1716 dot 10 dot camel at shapes dot demon dot co dot uk> <CAHu5PrZmi72sW3KmJA1puvn6n+wnm77EifiCQJf0-h8bmgd_yw at mail dot gmail dot com>
On 01/07/2015 04:57 PM, Cyd Haselton wrote:
> Adding -fno-lto to CFLAGS in the 4.9 libgcc Makefile worked.
> Libgcc_s.so built and linked successfully. I will add this to my list
> of build notes
Ah, good. That was a very, very difficult thing to debug because the
runtime error from fakechroot looked so much like a linker error, even
to the point of producing the same error message. It's probably the
hairiest thing I've ever helped debug on gcc-help.
> Thanks everyone for all of your help and patience. Anything else you
> need from me?
It's be nice to see if you can do a clean build with the --disable-lto
configure option. Then we can think about how to auto-disable it in the
gcc configury.
Andrew.