Chris Johns commented on a discussion on source-builder/config/gcc-common-1.cfg: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/35#note_110904 > + # be cut with ':' because _configdir contains 4 copies of > + # the same path > + %define rtems_configdir %(echo %{_configdir} | cut -d':' -f1) > + > + # Path to the location of the template script. > + %define stdcxx_template %{rtems_configdir}/stdcxx-template.py > + > + # Get the current GCC version of the target being built. > + %define rsb_rtems_gcc_version %(%{_bindir}/%{_target}-gcc --version | > head -1 | awk '{print $3}') > + > + # Path to the target location of the script: gdb/python > + %define stdcxx_script %{_prefix}/share/gdb/python/rtems/stdcxx.py > + > + # Modify the template script and update the current GCC version > + # and place it in the target location. > + cat %{stdcxx_template} | sed > "s/@RSB_GCC_VERSION@/%{rsb_rtems_gcc_version}/g" > %{stdcxx_script} Where does `gcc-pre-install.cfg`get included? I would include it in [rtems/config/tools/rtems-gcc-13.3-newlib-head.cfg](https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/blob/main/rtems/config/tools/rtems-gcc-13.3-newlib-head.cfg) and then you should not need `rtems_build` because it is an RTEMS build. The define check in `gcc-common-1.cfg` can be macro name. Also the name of the file can be what it does and not the name of macro if that helps make things clearer? -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/35#note_110904 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
