Re: [uclibc-ng-devel] uclibc with gcc 8.3.1

On 22/02/20 01:21, Ata, John (US) wrote: Closest I have is: Using built-in specs. COLLECT_GCC=armv6zk-unknown-linux-uclibceabihf-gcc-8.3.0 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/lto-wrapper Target: armv6zk-unknown-linux-uclibceabihf Configured with: /var/tmp/portage/cross-armv6zk-unknown-linux-uclibceabihf/gcc-8.3.0-r1/work/gcc-8.3.0/configure --host=x86_64-pc-linux-gnu --target=armv6zk-unknown-linux-uclibceabihf --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/armv6zk-unknown-linux-uclibceabihf/gcc-bin/8.3.0 --includedir=/usr/lib/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/include --datadir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0 --mandir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/man --infodir=/usr/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/info --with-gxx-include-dir=/usr/lib/gcc/armv6zk-unknown-linux-uclibceabihf/8.3.0/include/g++-v8 --with-python-dir=/share/gcc-data/armv6zk-unknown-linux-uclibceabihf/8.3.0/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 8.3.0-r1 p1.1' --disable-esp --enable-libstdcxx-time --enable-poison-system-directories --with-sysroot=/usr/armv6zk-unknown-linux-uclibceabihf --disable-bootstrap --disable-__cxa_atexit --enable-tls --disable-multilib --disable-altivec --disable-fixed-point --with-float=hard --with-arch=armv6zk --with-float=hard --with-fpu=vfp --enable-libgomp --disable-libmudflap --disable-libssp --disable-libmpx --disable-systemtap --disable-vtable-verify --disable-libvtv --enable-lto --without-isl --disable-libsanitizer --enable-default-pie --enable-default-ssp Thread model: posix gcc version 8.3.0 (Gentoo 8.3.0-r1 p1.1) uclibc-ng version is 1.0.31. But I am aware it's not generating good ARM executables because of another bug. http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64-… appears to have a functional x86_64 toolchain, unless I'm mistaken, but this is quite likely to have rolled over to gcc-9.2 now. We certainly would have had 8.3.0 if this build series has been continuous over the past year or so. Is it specifically 8.3._1_ you're having a problem with? _______________________________________________ devel mailing list devel(a)uclibc-ng.org https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel