Error performing Make with External Toolchain
TWIMC:
I've been trying to get BUILDROOT to successfully "make" for several days to no avail. I'm trying to use the latest crosstool-NG toolchain, so I've specified
an external toolchain. I've selected the latest version of BUILDROOT and the latest kernel headers. I've selected glibc/eglibc and support for SSP, strong SSP
and C++ support. The first attempt I had the option for ulibc selected along with RPC and ran into an error, so I unselected RPC and changed to glibc/eglibc and
here's my "make" output:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
jb@jb-VirtualBox-dev:~/GitHub/buildroot$ make
/usr/bin/make -j1 O=/home/jb/GitHub/buildroot/output HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" syncconfig
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
toolchain-external-custom Configuring
toolchain-external-custom Building
/usr/bin/gcc -O2 -I/home/jb/GitHub/buildroot/output/host/include -DBR_CPU='"cortex-a53"' -DBR_ABI='"aapcs-linux"' -DBR_FPU='"neon-vfpv4"' -DBR_FLOAT_ABI='"hard"' -DBR_MODE='"arm"' -DBR_CROSS_PATH_SUFFIX='""' -DBR_CROSS_PATH_ABS='"/home/jb/workspace/toolchains/armv8-rpi3-linux-gnueabi hf/bin"' -DBR_SYSROOT='"arm-buildroot-linux-gnueabihf/sysroot"' -DBR_ADDITIONAL_CFLAGS='"-fstack-protector-strong",' -DBR2_PIC_PIE -DBR2_RELRO_FULL -s -Wl,--hash-style=both toolchain/toolchain-wrapper.c -o /home/jb/GitHub/buildroot/output/build/toolchain-external-custom/toolchain-w rapper
Quoted 1 line
Quoted 1 line
Quoted 1 line
toolchain-external-custom Installing to staging directory
/usr/bin/install -D -m 0755 /home/jb/GitHub/buildroot/output/build/toolchain-external-custom/toolchain-w rapper /home/jb/GitHub/buildroot/output/host/bin/toolchain-wrapper
ln: failed to create symbolic link '/home/jb/GitHub/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot /usr/lib': No such file or directory
make[1]: *** [package/pkg-generic.mk:309:/home/jb/GitHub/buildroot/output/build/toolchain-external-custom/.stamp_stag ing_installed] Error 1
make: *** [Makefile:84: _all] Error 2
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
I checked for the presence of the .sysroot/usr/lib directory noted in the error and it does not exist, all I have is a "lib" directory. If I try to issue a ls lib I get an error:
"ls: cannot access 'lib': Too many levels of symbolic links"
Not being familiar with the BUILDROOT process, I'm at a loss regarding what to do and need help.
Thank you.
John Blacker
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 3 lines · John
_TWIMC:_
I’ve been trying to get BUILDROOT to successfully “make” for several days to no avail. I’m trying to use the latest crosstool-NG toolchain, so I’ve specified
It's been many years since anyone has tried to use a crosstool-NG toolchain,
so YMMV.
Quoted 5 lines
an external toolchain. I’ve selected the latest version of BUILDROOT and the latest kernel headers. I’ve selected glibc/eglibc and support for SSP, strong SSP
and C++ support. The first attempt I had the option for ulibc selected along with RPC and ran into an error, so I unselected RPC and changed to glibc/eglibc and
here’s my “make” output:
When you change any of the toolchain options, you need to do a clean build
(i.e. "make clean; make").
Quoted 28 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
jb@jb-VirtualBox-dev:~/GitHub/buildroot$ make
/usr/bin/make-j1 O=/home/jb/GitHub/buildroot/output HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" syncconfigQuoted 3 lines
Quoted 3 lines
Quoted 3 lines
toolchain-external-custom Configuring
toolchain-external-custom Building
/usr/bin/gcc-O2 -I/home/jb/GitHub/buildroot/output/host/include(quoted diff) +0
-6-DBR_CPU='"cortex-a53"' -DBR_ABI='"aapcs-linux"' -DBR_FPU='"neon-vfpv4"' -DBR_FLOAT_ABI='"hard"' -DBR_MODE='"arm"' -DBR_CROSS_PATH_SUFFIX='""' -DBR_CROSS_PATH_ABS='"/home/jb/workspace/toolchains/armv8-rpi3-linux-gnueabihf/bin"' -DBR_SYSROOT='"arm-buildroot-linux-gnueabihf/sysroot"' -DBR_ADDITIONAL_CFLAGS='"-fstack-protector-strong",' -DBR2_PIC_PIE -DBR2_RELRO_FULL -s -Wl,--hash-style=both toolchain/toolchain-wrapper.c -o
/home/jb/GitHub/buildroot/output/build/toolchain-external-custom/toolchain-wrapperQuoted 1 line
Quoted 1 line
Quoted 1 line
toolchain-external-custom Installing to staging directory
/usr/bin/install-D -m 0755/home/jb/GitHub/buildroot/output/build/toolchain-external-custom/toolchain-wrapper/home/jb/GitHub/buildroot/output/host/bin/toolchain-wrapperln: failed to create symbolic link '
/home/jb/GitHub/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib': No such file or directorymake[1]: *** [
package/pkg-generic.mk:309:/home/jb/GitHub/buildroot/output/build/toolchain-external-custom/.stamp_staging_installed] Error 1
Quoted 7 lines
make: *** [Makefile:84:
_all] Error 2<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
I checked for the presence of the …sysroot/usr/lib directory noted in the error and it does not exist, all I have is a “lib” directory. If I try to issue a ls lib I get an error:
“ls: cannot access ‘lib’: Too many levels of symbolic links”
This directory is created by the "skeleton-init-common" package, and AFAICS
not changed by anything after that (although, to be honest, the logic of the external toolchain installation is sometimes a bit hard to follow).
Is it possible that you have a custom skeleton that does something weird?
Can you do "ls -l .../sysroot" ?
Regards,
Arnout
Quoted 5 lines
Not being familiar with the BUILDROOT process, I’m at a loss regarding what to do and need help.
Thank you.
Quoted 8 lines
John Blacker
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot