summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL22
1 files changed, 8 insertions, 14 deletions
diff --git a/INSTALL b/INSTALL
index 88525b94e3..273866e52f 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1659,7 +1659,7 @@ the particular platforms:
README.ce
-=item Open Zaurus
+=item arm-linux (Open Zaurus, N770, etc)
Cross/README
@@ -1688,19 +1688,13 @@ For some cross-compilation environments the Configure option
C<-Dinstallprefix=...> might be handy, see L<Changing the installation
directory>.
-About the cross-compilation support of Configure: what is known to
-work is running Configure in a cross-compilation environment and
-building the miniperl executable. What is known not to work is
-building the perl executable because that would require building
-extensions: Dynaloader statically and File::Glob dynamically, for
-extensions one needs MakeMaker and MakeMaker is not yet
-cross-compilation aware, and neither is the main Makefile.
-
-The cross-compilation setup of Configure has successfully been used in
-at least two Linux cross-compilation environments. The setups were
-both such that the host system was Intel Linux with a gcc built for
-cross-compiling into ARM Linux, and there was a SSH connection to the
-target system.
+About the cross-compilation support of Configure: it supports
+cross-compilation process up to building the miniperl executable.
+You should go this way if your platform is not supported for perl
+cross-compilation (i.e. it is not arm-linux, wince or another platform
+mentioned above).
+
+If this is your case, keep reading this section.
To run Configure in cross-compilation mode the basic switch that
has to be used is C<-Dusecrosscompile>.