AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-09-19 16:10:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove mention of i386-pc-linux-gnu.

Browse Source 
The GNU C Library does not support building for i386
therefore we remove mention of this configuration
from the INSTALL file.
This commit is contained in:
Carlos O'Donell 2013-03-12 21:25:40 -04:00
parent 4f510e3aee
commit e98cdb38ee
3 changed files with 18 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -1,3 +1,9 @@
2013-03-12 Carlos O'Donell <carlos@redhat.com>
* manual/install.texi (Configuring and compiling):
Mention i686 and i586.
* INSTALL: Regenerate.
2013-03-12 Roland McGrath <roland@hack.frob.com>
* sysdeps/init_array/elf-init.c: New file.

11
INSTALL
View File

@ -128,6 +128,11 @@ will be used, and CFLAGS sets optimization options for the compiler.
this can be prevented though there generally is no reason since it
creates compatibility problems.
`--enable-hardcoded-path-in-tests'
By default, dynamic tests are linked to run with the installed C
library. This option hardcodes the newly built C library path in
dynamic tests so that they can be invoked directly.
`--build=BUILD-SYSTEM'
`--host=HOST-SYSTEM'
These options are for cross-compiling. If you specify both
@ -141,9 +146,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=i586-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.

8
manual/install.texi
View File

@ -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.