Thank you very much Tomek! when you get NuttX compiled on FreeBSD, please run the similar commands like these:
$ xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=xtensa-esp32-elf-gcc COLLECT_LTO_WRAPPER=/usr/local/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper Target: xtensa-esp32-elf Configured with: /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include --with-newlib --enable-threads=no --disable-shared --with-pkgversion='crosstool-NG esp-2021r2-patch3' --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --enable-lto --enable-target-optspace --without-long-double-128 --disable-nls --enable-multiarch --enable-languages=c,c++ --disable-libstdcxx-verbose --enable-threads=posix --enable-gcov-custom-rtio --enable-libstdcxx-time=yes Thread model: posix gcc version 8.4.0 (crosstool-NG esp-2021r2-patch3) If you send just the last line above it fine, we only need to know the toolchain version and characteristic. $ xtensa-esp32-elf-size nuttx text data bss dec hex filename 75231 320 7736 83287 14557 nuttx BR, Alan On 10/8/22, Tomek CEDRO <to...@cedro.info> wrote: > Hey there Alan :-) > > I am working on FreeBSD / BSD: > 1. kconfig-frontends is now in the FreeBSD ports and packages. > 2. I need to fix the SEDvsGSED issue. > 3. Have some ideas on how to unify MAKEvsGMAKE. > 4. KConfig work to add BSD also needs to be done. > 5. All 2 to 4 would point to GNUvsBSD build tools unification so > things work out of the box on both GNU and BSD in the same way with no > local modifications. > > This is not yet into this release, but lots of other work is done, and > this seems to be a release that others also wait to go out in order to > add their patches.. thus +1 from me not to block the works.. otherwise > no rush from me as things are done when they are done :-) > > Best regards :-) > Tomek > > > > > > On Sat, Oct 8, 2022 at 1:37 PM Alan C. Assis <acas...@gmail.com> wrote: >> >> Hi everyone, >> >> As suggestion when voting for a new release, please send together the >> information about what compiler was used and the output of your >> toolchain "size". >> >> This is just a suggestion, but help us to know that you really tested >> the release and also it is used as reference to know if the size >> increased too much or if there is some discrepancies between different >> toolchains. >> >> Thank you for understanding. >> >> BR, >> >> Alan >> >> On 10/8/22, Tomek CEDRO <to...@cedro.info> wrote: >> > +1 from me :-) >> > >> > -- >> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >> > > > > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
