Chris Johns commented: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/136#note_144223


I have moved this issue to the 7.1 milestone because of 
https://gitlab.rtems.org/contrib/newlib-cygwin/-/merge_requests/4 and 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1096. The change to 
newlib updates the bitset macro to use an `unsgined` type as the `signed` type 
is undefined or implementation-defined. This change is a good test and time for 
this change to be introduced into RTEMS.

---

This purpose of this change is to:

1. Stop builds of `rtems.git` if the tools are out of date
2. Provide a suitable check in the processes to make sure changes in newlib are 
reviewed by this project. Newlib is a separate project and the RTEMS project 
needs to have some oversight for the RTEMS specific files critical parts of 
RTEMS depend on. Some `score` code uses code from newlib in important areas.
3. Document interface changes between newlib and `rtems.git` 

---

I propose added a string `nl:yyyy.mm.dd`  to the GCC version message after the 
newlib hash. This would be a `%define` checked in the common GCC build recipe 
as bring defined to catch all newlib hash instances. The define would be 
located where the newlib hashes are defined.

The newlib build tag is only updated if a newlib change effects `rtems.git` . 
Newlib hashes can change if there is no compatibility issue with `rtems.git`.

The newlib tag is a date in a neutral format. The date just needs to be later 
than date being replaced. I suggest it is the date the change to the newlib 
hash is made.

The `rtems.git` build system needs to check the `gcc` message string for the 
`nl` tag and if present check the date string against it's date string. If the 
newlib date is later the build stops and raises an error.

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


_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs

Reply via email to