This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
[COMMITTED] Remove references to i386-pc-linux-gnu from INSTALL andmanual.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 12 Mar 2013 21:13:48 -0400
- Subject: [COMMITTED] Remove references to i386-pc-linux-gnu from INSTALL andmanual.
Given that we've all agreed that i386 is no longer
officially supported, and that we already removed it
from the list of supported targets with adae8f5e
by Joseph in 2012-04-27, this patch removes the last
traces of i386-pc-linux-gnu from INSTALL and manual
recommendations. Instead update the example to talk
about i686 and i586.
Verified manual builds and looks good.
Checked in.
2013-03-12 Carlos O'Donell <carlos@redhat.com>
* INSTALL: Mention i686 and i586.
* manual/install.texi (Configuring and compiling): Likewise.
diff --git a/INSTALL b/INSTALL
index 9a0166b..167b506 100644
--- a/INSTALL
+++ b/INSTALL
@@ -141,9 +141,9 @@ will be used, and CFLAGS sets optimization options for the compiler.
native compile but use what you specify instead of guessing what
your system is. This is most useful to change the CPU submodel.
For example, if `configure' guesses your machine as
- `i586-pc-linux-gnu' but you want to compile a library for 386es,
- give `--host=i386-pc-linux-gnu' or just `--host=i386-linux' and add
- the appropriate compiler flags (`-mcpu=i386' will do the trick) to
+ `i686-pc-linux-gnu' but you want to compile a library for 586es,
+ give `--host=i686-pc-linux-gnu' or just `--host=i586-linux' and add
+ the appropriate compiler flags (`-mcpu=i586' will do the trick) to
CFLAGS.
If you specify just `--build', `configure' will get confused.
diff --git a/manual/install.texi b/manual/install.texi
index e36fb05..e6c1baf 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -172,10 +172,10 @@ the compiler and/or binutils.
If you only specify @samp{--host}, @code{configure} will prepare for a
native compile but use what you specify instead of guessing what your
system is. This is most useful to change the CPU submodel. For example,
-if @code{configure} guesses your machine as @code{i586-pc-linux-gnu} but
-you want to compile a library for 386es, give
-@samp{--host=i386-pc-linux-gnu} or just @samp{--host=i386-linux} and add
-the appropriate compiler flags (@samp{-mcpu=i386} will do the trick) to
+if @code{configure} guesses your machine as @code{i686-pc-linux-gnu} but
+you want to compile a library for 586es, give
+@samp{--host=i586-pc-linux-gnu} or just @samp{--host=i586-linux} and add
+the appropriate compiler flags (@samp{-mcpu=i586} will do the trick) to
@var{CFLAGS}.
If you specify just @samp{--build}, @code{configure} will get confused.