...
> This is normal. Configure does two link tests when checking for> dlopen. The 
> first one is just "gcc conftest.c" and the second one is> "gcc conftest.c 
> -dl". It is expected that the first link will fail,> and the second link will 
> succeed. The failure of the first link is> ignored because the second one 
> succeeded. After the second link, you> will see a "result: -ldl" line which 
> means the check for dlopen did> succeed and the result is that -ldl is 
> required.
> 
> If your build failed, the real failure is elsewhere.
> 
> Jim
...
 
I see there was a second dlopen and this did indeed succeed; compile 
successfully bulds and leaves the libcc1 directory. Following this I see build 
fail while compiling in subdirectory "arm-linux-gnueabihf/libgcc". The command 
line "make" shows this failure i libgcc:
 
checking for arm-linux-gnueabihf-gcc... /home/build/linaro/32bit/./gcc/xgcc 
-B/home/build/linaro/32bit/./gcc/ 
-B/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/bin/
 
-B/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/lib/
 -isystem 
/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/include
 -isystem 
/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/sys-include
 --sysroot=/usr/local/sysroot/arm-linux-gnueabihf  checking for suffix of 
object files... configure: error: in 
`/home/build/linaro/32bit/arm-linux-gnueabihf/libgcc':configure: error: cannot 
compute suffix of object files: cannot compileSee `config.log' for more 
details.Makefile:11325: recipe for target 'configure-target-libgcc' 
failedmake[1]: *** [configure-target-libgcc] Error 1
 
The libgcc config.log shows what seems to be the implication of needing to look 
at yet a different config.log, but the message does not provide any indication 
of what really went wrong:
 
configure:3653: checking for suffix of object filesconfigure:3675: 
/home/build/linaro/32bit/./gcc/xgcc -B/home/build/linaro/32bit/./gcc/ 
-B/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/bin/
 
-B/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/lib/
 -isystem 
/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/include
 -isystem 
/usr/local/arm-linux-gnueabihf/gcc-linaro-6.1-2016.07/arm-linux-gnueabihf/sys-include
 --sysroot=/usr/local/sysroot/arm-linux-gnueabihf   -c -g -O2  conftest.c 
>&5/home/build/linaro/32bit/./gcc/as: line 106: exec: -m: invalid optionexec: 
usage: exec [-cl] [-a name] [command [arguments ...]] [redirection 
...]configure:3679: $? = 1
configure: failed program was:| /* confdefs.h */| #define PACKAGE_NAME "GNU C 
Runtime Library"| #define PACKAGE_TARNAME "libgcc"| #define PACKAGE_VERSION 
"1.0"| #define PACKAGE_STRING "GNU C Runtime Library 1.0"| #define 
PACKAGE_BUGREPORT ""| #define PACKAGE_URL 
"http://www.gnu.org/software/libgcc/";| /* end confdefs.h.  */| | int| main ()| 
{| |   ;|   return 0;| }configure:3693: error: in 
`/home/build/linaro/32bit/arm-linux-gnueabihf/libgcc':configure:3696: error: 
cannot compute suffix of object files: cannot compileSee `config.log' for more 
details. 
Which config.log is the message referring to? I did not see anything which 
would indicate which subdirectory config.log would be relevant (and I see no 
other errors which are obvious). Since the same host PC is building the same 
Linaro software with config being almost identical to the aarch64 version, it 
seems like the armhf sysroot has to be involved, but I've seen nothing to 
narrow this down. Are there any suggestions on where to look or a hint of the 
true cause of the armhf build error?
 
Thanks!
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Reply via email to