diff options
author | Thomas Trepl (Moody) <thomas@linuxfromscratch.org> | 2022-02-16 05:45:10 +0100 |
---|---|---|
committer | Thomas Trepl (Moody) <thomas@linuxfromscratch.org> | 2022-02-16 05:45:10 +0100 |
commit | 738a4c13cd3ee902f2c6df385ef3f4c83d8854d6 (patch) | |
tree | 7efc9061c62c562ada87c944010dc06717157c61 /chapter05 | |
parent | 7158d799ac4f75aef565b34347f544b6096057f3 (diff) | |
parent | 83e41daaa6ee8e34264851b41cebacf2322cfb30 (diff) |
Automatic merge of trunk into multilib
Diffstat (limited to 'chapter05')
-rw-r--r-- | chapter05/libstdc++.xml | 17 |
1 files changed, 14 insertions, 3 deletions
diff --git a/chapter05/libstdc++.xml b/chapter05/libstdc++.xml index 190a3b18e..b24688c04 100644 --- a/chapter05/libstdc++.xml +++ b/chapter05/libstdc++.xml @@ -102,11 +102,22 @@ cd build</userinput></screen> <varlistentry> <term><parameter>--with-gxx-include-dir=/tools/$LFS_TGT/include/c++/&gcc-version;</parameter></term> <listitem> - <para>This is the location where the C++ compiler should search for the - standard include files. In a normal build, this information + <para>This specifies the installation directory for include files. + Because libstdc++ is the standard C++ library for LFS, this + directory should match the location where the C++ compiler + (<command>$LFS_TGT-g++</command>) would search for the + standard C++ include files. In a normal build, this information is automatically passed to the libstdc++ <command>configure</command> options from the top level directory. In our case, this information - must be explicitly given.</para> + must be explicitly given. + The C++ compiler will prepend the sysroot path + <filename class="directory">$LFS</filename> (specified building + GCC pass 1) to the include file search path, so it will actually + search in + <filename class="directory">$LFS/tools/$LFS_TGT/include/c++/&gcc-version;</filename>. + The combination of the <parameter>DESTDIR</parameter> + variable (in the <command>make install</command> command below) + and this switch ensures to install the headers there.</para> </listitem> </varlistentry> |