[Pkg-electronics-devel] How is gcc-arm-none-eabi different from upstream GCC?

[John Scott]

Hi,

I need to salvage Newlib, but before I can do that I need to change gcc-arm-none-eabi so it's responsible for building its own Newlib using a combined tree approach. For some reason when I take the gcc-arm-none-eabi sources and put them in a combined tree with Newlib, Newlib doesn't get built. That's funky, but I wonder what's the difference between these sources from ARM and upstream GCC anyway besides the fact that these sources are giving me trouble?

The copyright file makes the bold claim that the gcc-arm-none-eabi sources are under the same license terms as upstream GCC, so taken at face value that would imply no changes have been made which of course probably isn't the case.

Maybe I was setting up my combined tree wrong. I'll keep poking at it...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-electronics-devel/attachments/20230812/66f922b9/attachment.sig>