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_145103

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

The actual name is `Build` and not build date. The data for the label is a date and so it has already become a short hand name. See the #130 for the details.

The build key :smile: applies to the build of these tools as a set which is gcc + newlib. A change in `rtems.git` that needs a new `newlib` could set the `rtems.git` to a date to a key value there are no tools for yet. However I would not see how you could test that without a build even a test build?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/227#note_145103
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/20260312/becacfab/attachment-0001.htm>