| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
No extra libc header build step is done, so no extra toolchain is needed
for preparing it.
This saves a significant amount of build time and disk space
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|
| |
|
|
| |
SVN-Revision: 36148
|
| |
|
|
| |
SVN-Revision: 34440
|
| |
|
|
|
|
| |
fixes parallel build on some systems
SVN-Revision: 33523
|
| |
|
|
| |
SVN-Revision: 33444
|
| |
|
|
|
|
| |
to avoid errors on copying
SVN-Revision: 32556
|
| |
|
|
|
|
|
|
|
|
|
| |
testing uclibc changes is tricky because the final gcc tends to miscompile
uclibc code or barf up internal compiler errors.
install binutils into $(TOOLCHAIN_DIR)/initial (without changing the configure
prefix) and copy it from there to $(TOOLCHAIN_DIR)/ so that the initial gcc
can be put into $(PATH) for the uclibc build, even if the final gcc
is already installed.
SVN-Revision: 32553
|
| |
|
|
|
|
| |
moving it back to $(TOOLCHAIN_DIR), this change makes the toolchain relocatable again, which should fix the SDK
SVN-Revision: 22723
|
|
|
initial, final), to clean up the dependency handling nastiness and to improve support for rebuilding parts of the toolchain
SVN-Revision: 22319
|
