mirror of
https://github.com/motioneye-project/motioneyeos.git
synced 2025-07-28 13:46:32 +00:00
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>
This commit is contained in:
parent
f6ec679f7b
commit
167302e722
@ -676,12 +676,9 @@ endif
|
|||||||
then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>,
|
then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>,
|
||||||
<code>ARCH-linux-ld</code>, etc.</p>
|
<code>ARCH-linux-ld</code>, etc.</p>
|
||||||
|
|
||||||
<p><b>Important</b>: do not try to move a gcc-3.x toolchain to another
|
<p>It is possible to relocate the toolchain — but
|
||||||
directory — it won't work because there are some hardcoded paths
|
then <code>--sysroot</code> must be passed every time the compiler
|
||||||
in the gcc-3.x configuration. If you are using a current gcc-4.x, it is
|
is called to tell where the libraries and header files are.</p>
|
||||||
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
|
<p>It is also possible to generate the Buildroot toolchain in a
|
||||||
directory other than <code>output/staging</code> by using the <code>
|
directory other than <code>output/staging</code> by using the <code>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user