[RTEMS Project] #4768: Use tarballs for stable versions development tools

[RTEMS trac]

#4768: Use tarballs for stable versions development tools
---------------------------+-----------------------
 Reporter:  Joel Sherrill  |       Owner:  (none)
     Type:  defect         |      Status:  reopened
 Priority:  normal         |   Milestone:  6.1
Component:  tool           |     Version:  6
 Severity:  blocker        |  Resolution:
 Keywords:                 |  Blocked By:
 Blocking:                 |
---------------------------+-----------------------
Changes (by Chris Johns):

 * status:  closed => reopened
 * resolution:  worksforme =>


Comment:

 I am reopening this ticket. The severity is blocker and if a release is
 not to used upstream released tarball files we need a clear reason why.

 The RSB is not using GCC released sources and the current
 [https://git.rtems.org/rtems-source-builder/tree/rtems/config/tools/rtems-
 gcc-10-newlib-head.cfg rtems/config/tools/rtems-gcc-10-newlib-head.cfg]
 shows this.

 If you look at the
 [https://ftp.rtems.org/pub/rtems/releases/5/5.3/sources/ 5.3 sources] you
 will see gcc tarballs are used, eg `gcc-9.3.0.tar.xz`. As things are an
 RTEMS 6 release will end up with a file called `gnu-mirror-gcc-
 92b44cf,tar.gz`.

 Where is the repo this comes from?

 The name `gnu-mirror-gcc` is confusing unless you understand what is going
 on?

 How do you track the integrity of the repo used once you manage to find
 it?

 I think we should be using a GCC release tarball of code in releases.

--
Ticket URL: <http://devel.rtems.org/ticket/4768#comment:3>
RTEMS Project <http://www.rtems.org/>
RTEMS Project