Newlib nano support for arm-none-eabi-gcc toolchain

[ekawahyu (Ekawahyu Susilo)]

Hi, would it be possible to add newlib nano support for arm-none-eabi-gcc toolchain? Thank you.

[denis-fr (Denis)]

Hello,
I have the same request.
"newlib-nano is now integrated in the main newlib source tree. Building newlib-nano is now a matter of specifying the right configure option." according to this discussion: ​https://answers.launchpad.net/gcc-arm-embedded/+question/244125

I try to do it, it is not very clean but it seems to work:

1. Update arm-none-eabi-gcc Portfile to get last newlib version and allow libgloss library to be compiled (as variant).
   
2. Small change in group crossgcc-1.0.tcl (/opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/crossgcc-1.0.tcl) to make it reusable: change all gcc-${version} by gcc-${crossgcc.version}
   
3. Create a arm-none-eabi-newlib-nano Portfile to add *_nano.a files. To do it I recompile a gcc+newlib with specific configure option + -Os optimization. And them rename *.a files to *_nano.a files (others files are discard).

This seems to works.

[denis-fr (Denis)]

diff Portfile arm-none-eabi-gcc

[denis-fr (Denis)]

Portfile arm-none-eabi-gcc with newlib 2.4.0

[denis-fr (Denis)]

change all gcc-${version} by gcc-${crossgcc.version}

[denis-fr (Denis)]

Portfile for newlib nano

[denis-fr (Denis)]

Cc Me!

[mf2k (Frank Schima)]

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers arm-none-eabi-gcc), if any.

[mf2k (Frank Schima)]

#53744

[mf2k (Frank Schima)]

• Why is this in a variant called libgloss? Is there a reason not to always add --with-libgloss?
• Does it require any dependencies?

[mojca (Mojca Miklavec)]

I was looking through all the tickets related to this port due to another unrelated problem.

newlib has been updated in the meantime to 3.0.0, even though an even newer version seems to be available at the moment (3.0.0.20180831, I can update to that one if needed), and the port has been simplified to quite some extent. We could also switch to gcc 8.

Would you be willing to review the patches with respect to the current state of the port? (ideally with a PR, so that it gets more attention from others as well, but patches are also ok.) I would like to address this ticket, but I don't know how to properly test and there have been quite some changes in the meantime. (We are somewhat understaffed, so it's a pity that some tickets get overlooked; nonmaintained ports as this one are most problematic.)

Not sure if this is related or not: #57572.

[mojca (Mojca Miklavec)]

See ​https://github.com/macports/macports-ports/pull/5584

[mojca (Mojca Miklavec)]

In 569684dbbe8d87a10728a9d9f2a4854b72d54fe2/macports-ports (master):

crossgcc: add symlink to libgloss

Closes: #51397
Closes: #57572

[mojca (Mojca Miklavec)]

In 8188ed1d3a237186b54ee3cc7c9078008b69d50b/macports-ports (master):

arm-none-eabi-gcc: update to 9.2.0

See: #51397
See: #57572