Bug 2395551

Summary:	Please branch and build arm-none-eabi-gcc-cs in epel10.0
Product:	[Fedora] Fedora EPEL	Reporter:	Alex Reid <alex>
Component:	arm-none-eabi-gcc-cs	Assignee:	Michal Hlavinka <mhlavink>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	epel-packagers-sig, mhlavink
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Reid 2025-09-15 22:55:48 UTC

Please branch and build arm-none-eabi-gcc-cs in epel10.0

In addition, the packages arm-none-eabi-binutils-cs, arm-none-eabi-gcc-cs-c++, and arm-none-eabi-newlib are related and linked packages. If desired I can create tickets for each one individually, but it made sense to me to create a single ticket because they are all part of one toolchain.

arm-none-eabi-gcc-cs is available in epel10.1 and epel10.2, but not available in epel10.0. By default, my install of AlmaLinux adds the epel10.0 repository. In order to install this toolchain, I manually install with —-releasever=10.1 . After doing so, the install gives no errors, and I am able to use the tools.

With that command, I am able to install the package, which is why I selected low severity. However it is a useful cross compiler and part of my workflow; I believe other users of enterprise Linux who are using 10.0 versions would benefit from its inclusion, and then no modification of repo files would be needed.