summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2011-01-30 15:37:50 +0100
committerPeter Korsgaard <jacmet@sunsite.dk>2011-01-30 20:13:44 +0100
commitae3ae906e5b910f062c15db7fab089c8cd657994 (patch)
treee4e43b4f93b65a291d5395a14f70309cbf6cb054
parent07cb06962c5a9326bf30713ee0a6ee2fd6a67323 (diff)
documentation: mention we can't use the distro toolchain as external
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
-rw-r--r--docs/buildroot.html9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html
index f1721ea41..36297e099 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -778,6 +778,15 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
</ul>
+ <p>We also do not support using the distribution toolchain (i.e
+ the gcc/binutils/C library installed by your distribution) as the
+ toolchain to build software for the target. This is because your
+ distribution toolchain is not a "pure" toolchain (i.e only with
+ the C/C++ library), so we cannot import it properly into the
+ Buildroot build environment. So even if you are building a system
+ for a x86 or x86_64 target, you have to generate a
+ cross-compilation toolchain with Buildroot or Crosstool-NG.</p>
+
<h2 id="add_packages">Adding new packages to Buildroot</h2>
<p>This section covers how new packages (userspace libraries or