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: Cyd Haselton <chaselton at gmail dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Mon, 5 Jan 2015 10:13:36 -0600
- 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> <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> <CAHu5Prav-nfzfHPoKJvJgy2VDFgFJmeJur-60hO9vGrtFgeCTA at mail dot gmail dot com> <CAHu5Prag8XZ56iyGnnhy_NPO6FC_07jV76vmeqcHMc0n7kDNuA at mail dot gmail dot com> <54AA5ED4 dot 7010700 at redhat dot com> <CAHu5PraFq7odtgFsPg5wL-ESeUd9M0x9iErj0Ywd8UpvsQw=pw at mail dot gmail dot com> <54AA719A dot 3090905 at redhat dot com>
On Mon, Jan 5, 2015 at 5:12 AM, Andrew Haley <aph@redhat.com> wrote:
> On 05/01/15 10:29, Cyd Haselton wrote:
>> On Mon, Jan 5, 2015 at 3:52 AM, Andrew Haley <aph@redhat.com> wrote:
>>> On 05/01/15 01:23, Cyd Haselton wrote:
>>>
>>> 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.
>>
>> See the list of commands I posted for the 4.8.4 libgcc build...both
>> are exactly the same.
>
> Okay, so the input files are different. Look at whichever input file
> supplies dlopen in 4.8 and see if it doesn't supply dlopen in 4.9.
>
>> I can try again to manually re-run both commands (see previous emails
>> for exact command) but if one succeeds and one fails i'm not sure how
>> that would help diagnose the issue or provide info that would do the
>> same.
>
> It gives us exactly what we need. Look in the input files. See
> which one supplies dlopen.
>
>> Wouldn't it be more helpful if I post the differences between both
>> buuld dirs...something that would indicate why one build failed and
>> the other didn't?
>
> You need to look inside the files with "nm" or something similar.
>
> Andrew.
>
>
I'm guessing because I haven't received a reply yet but here's the
first few lines of 'cat gcc/nm' run in both the 4.8 and 4.9 build dirs
4.9 build
# Invoke as, ld or nm from the build tree.
ORIGINAL_AS_FOR_TARGET="/usr/gcc-4.9.2/bin/as"
ORIGINAL_LD_FOR_TARGET="/usr/gcc-4.9.2/bin/ld"
ORIGINAL_LD_BFD_FOR_TARGET="/usr/gcc-4.9.2/bin/ld.bfd"
ORIGINAL_LD_GOLD_FOR_TARGET="/usr/gcc-4.9.2/bin/ld.gold"
ORIGINAL_PLUGIN_LD_FOR_TARGET="/usr/gcc-4.9.2/bin/ld"
ORIGINAL_NM_FOR_TARGET="/usr/gcc-4.9.2/bin/nm"
4.8 build
# Invoke as, ld or nm from the build tree.
ORIGINAL_AS_FOR_TARGET="/usr/gcc-4.8.4/bin/as"
ORIGINAL_LD_FOR_TARGET="/usr/gcc-4.8.4/bin/ld"
ORIGINAL_PLUGIN_LD_FOR_TARGET="/usr/gcc-4.8.4/bin/ld"
ORIGINAL_NM_FOR_TARGET="/usr/gcc-4.8.4/bin/nm"