summaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@suse.de>2001-03-27 05:32:26 +0000
committerAndreas Jaeger <aj@suse.de>2001-03-27 05:32:26 +0000
commit4a5b72ff790f1e86ff6a5200baa3b9feddc6febc (patch)
tree932dbf8cae67b36fb83f155dcbda658aff7b8228 /FAQ.in
parentdd68573b5c7844aab361507935c046b4da435c7e (diff)
Mention s390x.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in5
1 files changed, 3 insertions, 2 deletions
diff --git a/FAQ.in b/FAQ.in
index 67a54ba229..f06569ace4 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -38,6 +38,7 @@ in the future, are:
mips*-*-linux-gnu Linux-2.x on MIPS
ia64-*-linux-gnu Linux-2.x on ia64
s390-*-linux-gnu Linux-2.x on IBM S/390
+ s390x-*-linux-gnu Linux-2.x on IBM S/390 64-bit
Ports to other Linux platforms are in development, and may in fact work
already, but no one has sent us success reports for them. Currently no
@@ -1023,9 +1024,9 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
?? When recompiling GCC, I get compilation errors in libio.
-{BH} You are trying to recompile gcc 2.95.2? Use gcc 2.95.2.1 instead.
+{BH} You are trying to recompile gcc 2.95.2? Use gcc 2.95.3 instead.
This version is needed because the fpos_t type and a few libio internals
-have changed in glibc 2.2, and gcc 2.95.2.1 contains a corresponding patch.
+have changed in glibc 2.2, and gcc 2.95.3 contains a corresponding patch.
? Source and binary incompatibilities, and what to do about them