RFC: Maintaining gcc-avr

Background

Alpine now has support for quite a bunch of cross compilation toolchains for embedded targets. All corresponding binutils packages are provided by community/binutils-cross-embedded. GCC is provided for most as subpackages of testing/gcc-cross-embedded and testing/newlib. The single exception is community/gcc-avr.

Proposal

The package community/gcc-avr should be dropped and instead AVR support added to testing/gcc-cross-embedded.

This would require the following MRs to get in:

• !13612 (closed) - An updated of community/binutils-cross-embedded
  • BEWARE: This will break compilation with communicty/gcc-avr. I'm not 100% sure why the toolchains behave differently, but I believe it is due to the enabled multilib support in testing/gcc-cross-embedded.
  • Thus, it should be decided upon the fate of it prior to merging this
• !13567 (closed) - Addition of AVR to testing/gcc-cross-embedded
  • This depends on the binutils update above
• !13613 (merged) - Compilation fix of community/avr-libc
  • I'm not sure if this is only needed with the new toolchain; I didn't test compilation with the current one.
  • In any case, this should be fine to merge, as this won't hurt with the existing toolchain

Issues

• Can a package in testing replace a package in community?
  • If not, would gcc-cross-embedded be considered for moving to community. (There was already some discussion on moving it to either community or even to main to help with compilation of some ARM firmware needed to boot postmarket OS
• The update in binutils will break the current gcc-avr. It would be good to merge the GCC MR swiftly once the binutils package is updated, so that the AVR toolchain becomes operational again soon after.f