Android Native GCC 4.9.2 Build Fails at Dynamic libgcc

[Andrew Haley]

On 01/06/2015 06:08 PM, Brian Drummond wrote:
> On Fri, 2015-01-02 at 16:09 -0600, Cyd Haselton wrote:
> 
> Looking back through this thread...
>>
>> 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.  
> 
> Look at the same section in the 4.8 libgcc config.log... does it have
> the same oddity (below)?
> 
>> 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:
> (identical to mine ... setting gcc_no_link=no or yes)
> 
> Different host system, different build, etc, but...
> 
> configure:3389: /home/brian/Projects/ghdl-0.32/build/./gcc/xgcc
> -B/home/brian/Projects/ghdl-0.32/build/./gcc/
> -B/opt/ghdl-0.32/x86_64-unknown-linux-gnu/bin/
> -B/opt/ghdl-0.32/x86_64-unknown-linux-gnu/lib/
> -isystem /opt/ghdl-0.32/x86_64-unknown-linux-gnu/include
> -isystem /opt/ghdl-0.32/x86_64-unknown-linux-gnu/sys-include    -o
> conftest -g -O2   conftest.c  >&5
> /usr/bin/ld: cannot find crtbegin.o: No such file or directory
> /usr/bin/ld: cannot find -lgcc
> collect2: error: ld returned 1 exit status
> 
> Different failure, (to be expected, it's a test) but my question is...
> what are fakechroot and dlopen doing in your 4.9 config.log? 

Good point.  I wonder what fakechroot has to do with any of this?
fakechroot should have its own version of dlopen in libfakechroot.so.

But why on Earth is fakechroot in use when building gcc?

Andrew.