add what should be done after completing the toolchain and a note of warning

that many packages cannot be succesfully cross compiled.

svn path=/nixpkgs/trunk/; revision=4457

1 files changed, 15 insertions, 0 deletions

diff --git a/maintainers/docs/cross.txt b/maintainers/docs/cross.txt
index c79c571dee97..5ae2787d7998 100644
--- a/maintainers/docs/cross.txt
+++ b/maintainers/docs/cross.txt
@@ -314,3 +314,18 @@ too. Earlier on in the build process these flags are used to compile important
 files like libgcc.a by the host system gcc, which does need to be linked
 to glibc. To make this work correctly you will need to carefully juggle
 with compilation flags. This is still work in progress for Nix.
+
+
+---
+
+After succesfully completing the whole toolchain you can start building
+packages with the newly built tools. To make everything build correctly
+you will need a stdenv for your target platform. Setting up this platform
+will take some effort. Right now there is a very experimental setup for
+arm-linux, which needs to be cleaned up before it is production ready.
+
+Please note that many packages are not well suited for cross-compilation.
+Even though the package itself might be very well portable often the
+buildscripts are not. One thing that we have seen that causes frequent
+build failures is the use of the LD variable. This is often set to 'ld'
+and not $(CROSS)-ld.