On Fri, Jan 2, 2015 at 5:55 AM, Andrew Haley <aph@xxxxxxxxxx> wrote:
> On 01/02/2015 11:48 AM, Cyd Haselton wrote:
>> On Fri, Jan 2, 2015 at 4:38 AM, Andrew Haley <aph@xxxxxxxxxx> wrote:
>>> On 01/02/2015 10:32 AM, Cyd Haselton wrote:
>>>
>>> Okay, so if the commands are identical you need to run them by hand in
>>> the correct directory to see what is different. if the command which
>>> failed in 4.9 is exactly the same as the command which succeeded
>>> in 4.8 its input files must be different, and in particular dlopen()
>>> must be defined in one of the input files or the user of dlopen()
>>> must not be there in 4.8.
>>>
>> Thanks to the inability to write to extednal storage there is not much
>> space to work with on my android device. Keeping both the 4.8.4 and
>> the 4.9.2 builds plus the build GCC on device eats up nearly all of
>> it.
>
> Sure, but it never even occurred to me that having gone this far you'd
> delete the build tree! That's the problem with trying to debug
> problems like this by mail. If you can login to the device then you
> can copy a tree from it, I would have thought.
>
>> That being said...
>>
>> I still have the build logs and therefore the commands for the libgcc
>> link, but the list of input files is huge. I can review them, but if I
>> need to post them here should I use a link to a file or just copy and
>> paste everything?
>
> Neither. Sorry, I think you need to be able to run the commands by
> hand. I can't think of any other way: we really need to be able to
> compare the working and non-working trees.
>
> Andrew.
While the 4.8.4 build is re-running on device here's a related piece of info.
The config.log for libgcc reflects the dlopen error, but for whatever
reason it doesn't fail configure. Also I can't determine what
configure is testing for where it displays the error in config.log.
Here's the error in config.log:
configure:3389: /bld/gcc/builddir-4.9/./gcc/xgcc
-B/bld/gcc/builddir-4.9/./gcc/
-B/usr/gcc-4.9.2/arm-linux-androideabi/bin/
-B/usr/gcc-4.9.2/arm-linux-androideabi/lib/ -isystem
/usr/gcc-4.9.2/arm-linux-androideabi/include -isystem
/usr/gcc-4.9.2/arm-linux-androideabi/sys-include
--sysroot=/usr/gcc-4.9.2/sysroot -o conftest -g -O2 -Wall -O
-mandroid -mbionic conftest.c >&5 fakechroot: dlopen:
undefined symbol: dlopen
collect2: error: ld returned 1 exit status
And here's line 3389-97 in the configure script:
3389 if { { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$ac_link\""; } >&5
3390 (eval $ac_link) 2>&5
3391 ac_status=$?
3392 $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
3393 test $ac_status = 0; }; then :
3394 gcc_no_link=no
3395 else
3396 gcc_no_link=yes
3397 fi
