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

[Keith Packard]

> 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.

I'm not sure how that's supposed to work -- the usual process for
building gcc takes three steps:

 1. Build GCC in bootstrap mode that skips compiling libstdc++.
 2. Build the C library.
 3. Build GCC in full mode that builds libstdc++ using the installed C
    library.

Right now, Debian isolates these into three separate packages so that
users aren't tied to a specific C library, (or, in fact, any C library
at all).

(that leaves aside the question as to why you'd want to revive newlib at
all; it's not a great choice for embedded systems).

-- 
-keith
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-electronics-devel/attachments/20230812/ce9ff175/attachment.sig>