RTEMS Source Builder | rtems/config: Define gcc_build_date for targets with odd GCC (!231)

[Joel Sherrill (@joel)]

Joel Sherrill created a merge request: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/231

Project:Branches: joel/rtems-source-builder:make-edge-work-for-all-targets to rtems/tools/rtems-source-builder:main
Author:   Joel Sherrill
Assignee: Joel Sherrill


## Summary

The _edge_ configuration reflects the development version of GCC and newlib. Unfortunately, some target architectures are known to not work with the bleeding edge. These changes enable _edge_ to build for all targets and produce the closest to the "bleeding edge" as possible while avoiding major known issues.

- Microblaze requires a Xilinx GCC because all of the modifications have not been sent upstream.
- NIOS2 requires older tools because support for the architecture has been removed from the GNU tools.
- The aarch64 requires a GCC with ilp32 support. Once rtems 8.1 is out, this target can move to the same GCC version used by other
- targets.

Also included in this MR are patches to define _gcc_build_date_ for configurations that were missed when it was initially added.


## Generative AI

None


<!-- Default settings, if it is a dropdown it will set after submission -->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/231
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/20260317/c2748099/attachment-0001.htm>