RTEMS Source Builder | Add an RTEMS tools date to gcc version string (#130)

[Chris Johns (@chris)]

Chris Johns created an issue: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/130



## Summary

This issue is about adding a date to the GCC version string as a build indicator. RTEMS GCC builds of the 7 `next` tools currently gives:

```
$ /opt/work/rtems/7-next/bin/aarch64-rtems7-gcc --version
aarch64-rtems7-gcc (GCC) 15.2.0 20250808 (RTEMS 7, RSB 3d1db73ef0de7cc396183f6c599a301f355d2bba, Newlib 038afec1)
Copyright (C) 2025 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```

The first line of the version string is the RSB macro [%{gcc_version_message}](https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/blob/main/rtems/config/rtems-base.bset?ref_type=heads#L26). The `Newlib` value is a hash or a version depending on the specific configuration and with that it hard to work with in [RTEMS](https://gitlab.rtems.org/rtems/rtos/rtems) as we need something we can compare against for equal or higher such as a number or a date.

# Proposal

The proposal is to add a build field to the release that is manually set in the RSB and picked up by `current`, `next` and `edge` builds of the tools. The build date appears in the GCC version string. For example:

```
aarch64-rtems7-gcc (GCC) 15.2.0 20250808 (RTEMS 7, Build 20251001, RSB 3d1db73ef0de7cc396183f6c599a301f355d2bba, Newlib 038afec1)
```

The build field has one mandated item a date and an optional second field for `next` and `edge` builds. The second field is informational.

## Using Build

A package that depends in specific builds of tools can query GCC during its configure stage, extract the build field date and compare it to a threshold date it holds. The setting of the date in the RSB is manual and the updating of the date in a package is also manual.

Any support has to handle no build field being present and if no build date is present the tool are accepted as OK to use.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/130
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/20251002/fdbcdb41/attachment-0001.htm>