Android Native GCC 4.9.2 Build Fails at Dynamic libgcc

[Cyd Haselton]

On Fri, Dec 26, 2014 at 4:02 PM, Andrew Haley <aph@redhat.com> wrote:
> On 26/12/14 20:05, Cyd Haselton wrote:
>> On Thu, Dec 25, 2014 at 4:08 AM, Cyd Haselton <chaselton@gmail.com> wrote:
>>> On Thu, Dec 25, 2014 at 4:52 AM, Cyd Haselton <chaselton@gmail.com> wrote:
>>>> On Thu, Dec 25, 2014 at 3:27 AM, Andrew Haley <aph@redhat.com> wrote:
>>>>> On 24/12/14 20:54, Cyd Haselton wrote:
>>>>>> Although I'm not sure if this has anything to do with the libgcc issue
>>>>>> i'm seeing...
>>>>>
>>>>> It probably isn't.  The problem I'm having right now is that I don't
>>>>> know why 4.8.x works.  I have no Android development system to find
>>>>> out.  It'd be really cool if you could find out where 4.8.x gets the
>>>>> necessary -ldl from.
>>>>>
>>>>> Andrew.
>>>>>
>>>
>>> For the link-command part of -dumpspecs? Or elsewhere?
>>> Would it help if I posted the entire contents of dumpspecs?
>>
>> Follow up to make sure i'm parsing the correct location for -ldl inclusion.
>
> The only way to proceed: look at the output when compiling 4.8 and see
> where the -ldl comes from, then look at the makefiles.  I have no
> tricks, I'm afraid.
>
> Andrew.
>
>
Just to make sure I'm on the same page:
Rebuild 4.8.3 and/or upgrade to 4.8.4 and keep build directory
Compare 4.8.4 build dir (or build dir of component that failed) to
corresponding 4.9.2 location.

That about right?