On Tue, Jan 6, 2015 at 12:08 PM, Brian Drummond <brian@xxxxxxxxxxxxxxxxxx> 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)? > > 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 No, the 4.8 config.log does not have the same oddity. I thought I'd posted what turns up in the 4.8 config log in the same area, but just in case, here it is: configure:3374: /bld/gcc/builddir-4.8/./gcc/xgcc -B/bld/gcc/builddir-4.8/./gcc/ -B/usr/gcc-4.8.4/arm-linux-androideabi/bin/ -B/usr/gcc-4.8.4/arm-linux-androideabi/lib/ -isystem /usr/gcc-4.8.4/arm-linux-androideabi/include -isystem /usr/gcc-4.8.4/arm-linux-androideabi/sys-include --sysroot=/usr/gcc-4.8.4/sysroot -o conftest -g -O2 -Wall -O -mandroid -mbionic conftest.c >&5 /usr/gcc-4.8.4/bin/ld: cannot find -lgcc_s /usr/gcc-4.8.4/bin/ld: cannot find -lgcc_s 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? > > They aren't in the configure script... It may be worth echoing > everything this test uses and, if something has been set to this value, > tracing back to see how it was set. Also, does this end up in the > Makefile as a result? Not that I can determine. I can 't figure out what that line of the configure is testing for, so I don't know where to look in the Makefile.
