Hi Gary, You can debug the compiler, but I don’t believe you can do an incremental build (though I haven’t tried). The reason is that it does bypass parts of the GCC build system, so doing a standard make after will most likely not work. Regards, Tamar From: Gary Oblock <gary@xxxxxxxxxxxxxxxxxxx> Sent: Thursday, June 23, 2022 8:36 PM To: Tamar Christina <Tamar.Christina@xxxxxxx>; Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx> Subject: Re: More configure fun... Tamar, OK thanks I'll look into that. But I'm now curious about the caveat about not being able to debug the compiler. Could explain the reason? You well know that I'm an optimization guy and that I might get sucked into trying figure out why what I built is behaving in some manner or the other and possibly doing something about it. Thanks again. Gary ________________________________ From: Tamar Christina <Tamar.Christina@xxxxxxx<mailto:Tamar.Christina@xxxxxxx>> Sent: Thursday, June 23, 2022 7:43 AM To: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx<mailto:gcc-help@xxxxxxxxxxx>>; Gary Oblock <gary@xxxxxxxxxxxxxxxxxxx<mailto:gary@xxxxxxxxxxxxxxxxxxx>> Subject: Re: More configure fun... [EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.] Hi Gary, It looks like your original zephyr toolchain was built with crosstool-NG, have you considered using that to build your updated one? crosstool-ng does make it very easy to build a full cross toolchain. If you don't need to debug it it's probably by far the easiest way. You just fill in the target and options and it does the rest. Cheers, Tamar ________________________________ From: Gcc-help <gcc-help-bounces+tamar.christina=arm.com@xxxxxxxxxxx<mailto:gcc-help-bounces+tamar.christina=arm.com@xxxxxxxxxxx>> on behalf of Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx<mailto:gcc-help@xxxxxxxxxxx>> Sent: Thursday, June 23, 2022 6:57 AM To: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx<mailto:gcc-help@xxxxxxxxxxx>> Subject: More configure fun... I'm trying to configure a GCC 12 cross build like this: ../sources/configure --prefix=$BASE/install --disable-bootstrap --enable-language=c --disable-multilib --target=arm-zephyr-eabi --with-sysroot=/home/garyzepher/zephyr/lib/libc --disable-shared --enable-__cxa_atexit --disable-tm-clone-registry --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --enable-lto --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm' --enable-target-optspace --disable-nls --enable-multiarch --with-multilib-list=rmprofile --enable-languages=c,c++ --with-gnu-ld --with-gnu-as --enable-initfini-array The original cross compiler (GCC 10 based was configured like this: ../sources/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=arm-zephyr-eabi --prefix=/workdir/build/output/arm-zephyr-eabi --exec_prefix=/workdir/build/output/arm-zephyr-eabi --with-local-prefix=/workdir/build/output/arm-zephyr-eabi/arm-zephyr-eabi --with-headers=/workdir/build/output/arm-zephyr-eabi/arm-zephyr-eabi/include --with-newlib --enable-threads=no --disable-shared --with-pkgversion='crosstool-NG 1.24.0.378_e011758' --enable-__cxa_atexit --disable-tm-clone-registry --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --with-gmp=/workdir/build/build_arm/.build/arm-zephyr-eabi/buildtools --with-mpfr=/workdir/build/build_arm/.build/arm-zephyr-eabi/buildtools --with-mpc=/workdir/build/build_arm/.build/arm-zephyr-eabi/buildtools --with-isl=/workdir/build/build_arm/.build/arm-zephyr-eabi/buildtools --enable-lto --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm' --enable-target-optspace --disable-nls --enable-multiarch --with-multilib-list=rmprofile --enable-languages=c,c++ --with-gnu-ld --with-gnu-as --enable-initfini-array All those --with-* parameters don't seem to correlate with anything in the SDK and I haven't got a clue as of yet how to build a cross binutils for a Zephyer OS for the Arm Thumb-2 ISA. The build error I'm seeing at the ends of the log is: . . . The directory that should contain system headers does not exist: /home/gary/zephyr/zephyr/lib/libc/usr/include make[2]: *** [Makefile:3255: stmp-fixinc] Error 1 make[2]: Leaving directory '/home/gary/gcc_build_cross/objdir/gcc' make[1]: *** [Makefile:4527: install-gcc] Error 2 make[1]: Leaving directory '/home/gary/gcc_build_cross/objdir' make: *** [Makefile:2439: install] Error 2 These are the closest looking include directories that I have. If any of them will do what parameter lets me use it? ./zephyr/lib/libc/arcmwdt/include fcntl.h sys ./zephyr/lib/libc/newlib/include errno.h fcntl.h sys ./zephyr/lib/libc/minimal/include assert.h bits ctype.h errno.h fcntl.h inttypes.h limits.h math.h stdbool.h stdint.h stdio.h stdlib.h string.h strings.h sys time.h ./zephyr/lib/libc/armstdc/include stdint.h 😯 Gary CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Ampere Computing or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. Any unauthorized review, copying, or distribution of this email (or any attachments thereto) is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
