Suraj Kumar 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_109049 > %{__make} DESTDIR=$SB_BUILD_ROOT install > cd ${build_top} > > + # Path to the directory rtems/config. Tt needs to > + # 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}') I had talked about this with Chris here, please check out this thread when you find the time: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/5#note_108895 Chris had said: > Would it end up being confusing? How would know which value the variable > holds? Remember the gcc version internal to gcc may not match the version in > the macro `gcc_version`. For example we could have a git hash build of the > gcc 13 branch. This work needs to know the internal value to find the path > gcc will look. So, I resorted to finding the actual version from the target's GCC compiler itself. Hope that it clear. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/35#note_109049 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