On Mon, Jan 5, 2015 at 5:12 AM, Andrew Haley <aph@xxxxxxxxxx> wrote:
> On 05/01/15 10:29, Cyd Haselton wrote:
>> On Mon, Jan 5, 2015 at 3:52 AM, Andrew Haley <aph@xxxxxxxxxx> 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"
