diff options
| author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2010-11-24 11:59:02 +0100 |
|---|---|---|
| committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2010-11-24 11:59:02 +0100 |
| commit | 167302e722ed84dff2f673d88682444e4d0ef6ac (patch) | |
| tree | 25c147f2d5a7b4f66bcbcd25c52f354930787448 | |
| parent | f6ec679f7b290489e177457ae40bce28371a8d88 (diff) | |
documentation: Remove mention of gcc 3.x
We don't support gcc 3.x anymore, so get rid of 3.x-specific details
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
| -rw-r--r-- | docs/buildroot.html | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html index 571414b8f..333ea224d 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -676,12 +676,9 @@ endif then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>, <code>ARCH-linux-ld</code>, etc.</p> - <p><b>Important</b>: do not try to move a gcc-3.x toolchain to another - directory — it won't work because there are some hardcoded paths - in the gcc-3.x configuration. If you are using a current gcc-4.x, it is - possible to relocate the toolchain — but then <code>--sysroot</code> - must be passed every time the compiler is called to tell where the - libraries and header files are.</p> + <p>It is possible to relocate the toolchain — but + then <code>--sysroot</code> must be passed every time the compiler + is called to tell where the libraries and header files are.</p> <p>It is also possible to generate the Buildroot toolchain in a directory other than <code>output/staging</code> by using the <code> |