| 1 | CLFS-1.x NOTES
|
|---|
| 2 |
|
|---|
| 3 | None for now.
|
|---|
| 4 |
|
|---|
| 5 |
|
|---|
| 6 |
|
|---|
| 7 | CLFS SYSROOT METHOD NOTES
|
|---|
| 8 |
|
|---|
| 9 | .- If you want to install additional custom packages via "Add custom tools
|
|---|
| 10 | support" and/or select "Add blfs-tool support", be sure to review and edit
|
|---|
| 11 | their packages build scripts to follow the sysroot build method or you will
|
|---|
| 12 | end messing your host system. Be very careful with this.
|
|---|
| 13 |
|
|---|
| 14 | .- If you install additional packages not using the "Add custom tools support"
|
|---|
| 15 | feature (i,e, you will install it manually after finished the Makefile run)
|
|---|
| 16 | you will need to run manually the "Changing the Ownership Of The CLFS System"
|
|---|
| 17 | phase commands found in the book.
|
|---|
| 18 |
|
|---|
| 19 |
|
|---|
| 20 |
|
|---|
| 21 | CLFS EMBEDDED SYSTEMS NOTES
|
|---|
| 22 |
|
|---|
| 23 | .- Mips, WRT and ARM builds are broken due a book bug on the uClibc
|
|---|
| 24 | *ENDIAN* configuration settings.
|
|---|
| 25 |
|
|---|
| 26 | .- To install CBLFS packages you must to use the "Add custom tools support"
|
|---|
| 27 | feature. To learn how it works and how to use it, see the section titled
|
|---|
| 28 | "Adding Post-System Build Configuration Files and Extra Packages"
|
|---|
| 29 | found in README.CUSTOM. That is also applicable to bootloaders installation.
|
|---|
| 30 |
|
|---|
| 31 | .- If you install additional packages not using the "Add custom tools support"
|
|---|
| 32 | feature (i,e, you will install it manually after finished the Makefile run)
|
|---|
| 33 | you will need to run manually the "Changing the Ownership Of The CLFS System"
|
|---|
| 34 | phase commands found in the book.
|
|---|
| 35 |
|
|---|
| 36 | .- If your target is a MIPS wireless router, you must to select "mips" as
|
|---|
| 37 | your target architecture and "WRT - MIPS based wireless route" as your
|
|---|
| 38 | hardware platform.
|
|---|
| 39 |
|
|---|
| 40 | .- The backup & clean-up phases aren't run. This is to allow users to
|
|---|
| 41 | review the installed files and do a more in-deeper clean-up before creating
|
|---|
| 42 | the system tarball.
|
|---|
