RTEMS Source Builder | rtems: Add support for a build date in the gcc version message (!227)

[Chris Johns (@chris)]

Chris Johns commented on a discussion on rtems/config/tools/rtems-gcc-head-newlib-head.cfg: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/227#note_145061

 >  %include %{_configdir}/checks.cfg
 >  %include %{_configdir}/base.cfg
 >  
 > +%define gcc_build_date 2026.03.04

Yes that is the plan but it is optional. An issue has not been opened. I discussed this in https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1096#note_144219. 

I would like a key in the tools that defines the combined gcc and newlib versions. There are limited option as newlib is a hash and gcc can also be a hash.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/227#note_145061
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260311/d7ad27e5/attachment-0001.htm>