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>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Mon, 05 Jan 2015 09:52:20 +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> <CAHu5PrY0MUt--KbNCCbQ+4z8jwVHTVaRrE9d+TBwubs3dTzP5Q at mail dot gmail dot com> <CAHu5PrZ1QVLAPyexbqpSafcRuepVfxZdHv3avgFVqXKubC0jug at mail dot gmail dot com> <CAHu5PrYWjwmC7VtqsNSwezvYVvFcuj6EB9UUP_=RKxau5t+kNQ at mail dot gmail dot com> <549DDADB dot 4020707 at redhat dot com> <CAHu5PraJcUxrKcs36uc=njbbs7HLRr4+ozL04OzMEPVyZCDBUw at mail dot gmail dot com> <549EEEF6 dot 9030506 at redhat dot com> <CAHu5PrYG50rU-o7MrFkehdNpQ-KvXYmh6Ymr=OzmYe++V_Wppg 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> <54A68729 dot 6080004 at redhat dot com> <CAHu5Pr! bLdjp04a_NFVYEs9nqO=qr4hWKSQUA9wfJrz4uSxTocg at mail dot gmail dot com> <CAHu5Prav-nfzfHPoKJvJgy2VDFgFJmeJur-60hO9vGrtFgeCTA at mail dot gmail dot com> <CAHu5Prag8XZ56iyGnnhy_NPO6FC_07jV76vmeqcHMc0n7kDNuA at mail dot gmail dot co! m>
On 05/01/15 01:23, Cyd Haselton wrote:
> So I went ahead and after lots of trial and error managed to correctly
> run each of the above commands one by on in the
> arm-linux-androideabi/libgcc directory.
>
> The result:
>
> /usr/gcc-4.8.4/bin/ld:libgcc.map:1: syntax error in VERSION script
> collect2: error: ld returned 1 exit status
>
> which makes sense as the libgcc.map file is empty...though i'm not
> sure why as I ran the commands in the same order as the libgcc build,
> which completed successfully. Should I just do make clean && make in
> the arm-linux-androideabi/libgcc dir of both 4.8.4 and 4.9.2?
Hmm. Right now I would have thought that the only command you'd need
to run on both was the one which failed on 4.9, whatever that was. It
might not be a terrible idea to try to re-make the libcc dir, but it
may fail.
Andrew.