[MacPorts] #66355: arm-none-eabi-gcc: add newlib nano support

[MacPorts]

#66355: arm-none-eabi-gcc: add newlib nano support
-------------------------------------------------+-------------------------
 Reporter:  trail-coffee                         |      Owner:  (none)
     Type:  enhancement                          |     Status:  new
 Priority:  Normal                               |  Milestone:
Component:  ports                                |    Version:
 Keywords:  newlib, newlib-nano, nano, arm-      |       Port:  arm-none-
  none-eabi-gcc                                  |  eabi-gcc
-------------------------------------------------+-------------------------
 Port arm-none-eabi-gcc copies nano.specs and some projects looks for
 nano.specs as indication that newlib_nano libraries are installed. I saw
 [https://trac.macports.org/ticket/51397 ticket#51397] that looks like
 *_nano was supported at one time.

 I think the proper thing to do is either don't copy nano.specs (like the
 ubuntu arm-none-eabi-gcc install) or make the *_nano.a libraries using the
 instructions from ARM in the release notes
 [https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads here].
 Basically build with nano options in new build directory then use their
 [https://developer.arm.com/-/media/Files/downloads/gnu/12.2.mpacbti-
 bet1/manifest/copy_nano_libraries.sh?rev=0e6f4b41803a4bc192508eee02b8659b&hash=F8F0BD8CCFDBFC32221BBB35103B983F22702C7A
 copy_nano_libraries.sh].

 I think I can get it working with some guidance on the proper way to do
 things. Should this be a variant on arm-none-eabi-gcc and just fetch{} to
 use original newlib download, build with the options from the linaro
 manifest, and do the renames to _nano post-build?

-- 
Ticket URL: <https://trac.macports.org/ticket/66355>
MacPorts <https://www.macports.org/>
Ports system for macOS