diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 7b1595964..843aed83a 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -42,6 +42,24 @@ or as appropriate for the entry or if needed the entire day's listitem. --> + + 2016-08-12 + + + [bdubbs] - Update to diffutils-3.4. Fixes + #3964. + + + [bdubbs] - Update to iproute2-4.7.0. Fixes + #3965. + + + [bdubbs] - Update to util-linux 2.28.1. Fixes + #3966. + + + + 2016-08-11 diff --git a/chapter01/whatsnew.xml b/chapter01/whatsnew.xml index a93c7820f..95d67a78a 100644 --- a/chapter01/whatsnew.xml +++ b/chapter01/whatsnew.xml @@ -62,9 +62,9 @@ D-Bus-&dbus-version; - + Eudev &eudev-version; diff --git a/chapter05/adjusting.xml b/chapter05/adjusting.xml deleted file mode 100644 index e567da5a5..000000000 --- a/chapter05/adjusting.xml +++ /dev/null @@ -1,79 +0,0 @@ - - - %general-entities; -]> - - - - - Adjusting the Toolchain - - Now that the temporary C libraries have been installed, all - tools compiled in the rest of this chapter should be linked against - these libraries. In order to accomplish this, the cross-compiler's - specs file needs to be adjusted to point to the new dynamic linker - in /tools. - - This is done by dumping the compiler's specs file to a - location where it will look for it by default. - A simple sed substitution then alters the - dynamic linker that GCC will use. The principle here is to find all references - to the dynamic linker file in /lib - or possibly /lib64 if the host system - is 64-bit capable, and adjust them to point to the new location in - /tools. - - For the sake of accuracy, it is recommended to use a copy-and-paste - method when issuing the following command. Be sure to visually inspect the - specs file to verify that it has properly adjusted all references to the - dynamic linker location. Refer to for the default name - of the dynamic linker, if necessary. - - -SPECS=`dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/specs -$LFS_TGT-gcc -dumpspecs | sed \ - -e 's@/lib\(64\)\?/ld@/tools&@g' \ - -e "/^\*cpp:$/{n;s,$, -isystem /tools/include,}" > $SPECS -echo "New specs file is: $SPECS" -unset SPECS - - - At this point, it is imperative to stop and ensure that the basic - functions (compiling and linking) of the new toolchain are working as - expected. To perform a sanity check, run the following commands: - -echo 'int main(){}' > dummy.c -$LFS_TGT-gcc -B/tools/lib dummy.c -readelf -l a.out | grep ': /tools' - - If everything is working correctly, there should be no errors, - and the output of the last command will be of the form: - -[Requesting program interpreter: /tools/lib/ld-linux.so.2] - - Note that /tools/lib, or - /tools/lib64 for 64-bit machines - appears as the prefix of the dynamic linker. - - If the output is not shown as above or there was no output at all, - then something is wrong. Investigate and retrace the steps to find out - where the problem is and correct it. This issue must be resolved before - continuing on. Something may have gone wrong with the - specs file amendment above. In this case, redo the specs file amendment, - being careful to copy-and-paste the commands. - - Once all is well, clean up the test files: - -rm -v dummy.c a.out - - - - Building Binutils in the next section will serve as an additional check that - the toolchain has been built properly. If Binutils fails to build, it is an - indication that something has gone wrong with the previous Binutils, GCC, or Glibc - installations. - - diff --git a/general.ent b/general.ent index a8d32b07a..4bc08e4db 100644 --- a/general.ent +++ b/general.ent @@ -1,13 +1,13 @@ - + - + - + diff --git a/packages.ent b/packages.ent index d1bacee17..c535946df 100644 --- a/packages.ent +++ b/packages.ent @@ -122,10 +122,10 @@ - - + + - + @@ -325,10 +325,10 @@ - - + + - + @@ -606,10 +606,10 @@ - - + + - +