Age | Commit message (Collapse) | Author | Files | Lines |
|
A few facts:
- building the C library requires a proper core compiler
- core compiler is issued from one of the core passes
- the C library is required to build libstdc++
- newlib is only built for baremetal
- in bare metal, the final compiler is issued from one of the core passes
So we need to build the C library between core pass 1 and core pass 2.
The only place is eithe libc_headers() or libc_start_files(). The most
pertinent seems to be libc_start_files().
So we build newlib from libc_start_files(), and leave libc() empty.
|
|
The newlib FTP site does not like // downloads, and quickly
blocks the IP from the downloader.
Override the number of chunks when downloading newlib.
|
|
It is the responsibility of the caller to split the package name from
its version. It already knows that.
|
|
|
|
The newlib "team" rolls new releases about once a year (december).
This is quite a long time between releases, in case code was fixed.
So, allow user to use a CVS snapshot to benefit early from fixes
and enhancements to newlib.
|
|
build step:
- ./configure
- remove glibc-specific options
- pass the target CFLAGS in the correct variable
- make:
- build in //
finish step:
- print proper message in finish step
|
|
newlib handles the build/host/target a bit differently as one would expect:
build : not used
host : the nachine that builds newlib
target : the machine on which newlib will run
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|