diff options
author | Jeremy Utley <jeremy@linuxfromscratch.org> | 2004-12-04 20:53:03 +0000 |
---|---|---|
committer | Jeremy Utley <jeremy@linuxfromscratch.org> | 2004-12-04 20:53:03 +0000 |
commit | af133c3f42ecfac2892e1cd1eaf202575e932502 (patch) | |
tree | 2c202fba99d9004dd39b2ff5f4e6ce16618d75b0 /chapter06 | |
parent | 0a324b5241f112b6929ebd85591226ef7eb2d1bb (diff) |
Added new binutils fix_strip patch taken from upstream
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4354 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06')
-rw-r--r-- | chapter06/binutils.xml | 7 | ||||
-rw-r--r-- | chapter06/devices.xml | 9 |
2 files changed, 16 insertions, 0 deletions
diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml index 2dc90cb84..8a35d49a3 100644 --- a/chapter06/binutils.xml +++ b/chapter06/binutils.xml @@ -49,6 +49,13 @@ Therefore, if you have defined any environment variables that override default optimizations, such as CFLAGS and CXXFLAGS, we recommend un-setting or modifying them when building Binutils.</para> +<para>The current version of Binutils in use has a bug that causes strip to +remove necessary information from certain library files. This patch fixes +the problem:</para> + +<screen><userinput>patch -Np1 -i ../binutils-&binutils-version;-fix_strip-1.patc +h</userinput></screen> + <para>The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:</para> diff --git a/chapter06/devices.xml b/chapter06/devices.xml index 557b0d2c3..dc5de88b8 100644 --- a/chapter06/devices.xml +++ b/chapter06/devices.xml @@ -60,6 +60,15 @@ created:</para> <screen><userinput>mount -t devpts -o gid=4,mode=620 none /dev/pts mount -t tmpfs none /dev/shm</userinput></screen> + +<para>The <command>mount</command> commands executed above may result in the +following warning message:</para> + +<screen><computeroutput>can't open /etc/fstab: No such file or directory.</computeroutput></screen> + +<para>This file—<filename>/etc/fstab</filename>—has not +been created yet but is also not required for the file systems to be +properly mounted. As such, the warning can be safely ignored.</para> </sect2> |