mirror of
https://sourceware.org/git/glibc.git
synced 2024-12-23 11:20:07 +00:00
a01f19c8fb
This change does two things: * Treats a target i386-* as if it were i686. * Fails configure if the user is generating code for i386. We no longer support i386 code-generation because the i386 lacks the atomic operations we need in glibc. You can still configure for i386-*, but you get i686 code. You can't build with --march=i386, --mtune=i386 or a compiler that defaults to i386 code-generation. I've added two i386 entries in the master todo list to discuss merging and renaming: http://sourceware.org/glibc/wiki/Development_Todo/Master#i386 The failure modes are fail-safe here. You compile for i386, get i686, and try to run on i386 and it fails. The configure log has a warning saying we elided to i686. There is no situation that I can see where we run into any serious problems. The patch makes the current state better in that we get less confused users and we build successfully in more default configurations. The next enhancement would be to add --march=i?86 as suggested in #c20 of BZ#10062 for any i?86-* builds, which would solve the problem of a 32-bit compiler that defaults to i386 code-gen and glibc configured for i686-* target. Which previously failed at build time, and now will fail at configure time (requires adding --march=i686). Updated NEWS with BZ #10060 and #10062. No regressions. --- 2013-04-06 Carlos O'Donell <carlos@redhat.com> [BZ #10060, #10062] * aclocal.m4 (LIBC_COMPILER_BUILTIN_INLINED): New macro. * sysdeps/i386/configure.in: Use LIBC_COMPILER_BUILTIN_INLINED and fail configure if __sync_val_compare_and_swap is not inlined. * sysdeps/i386/configure: Regenerate. * configure.in: Build for i686 when configured for i386. * configure: Regenerate. * README: Remove i386 reference.
81 lines
3.4 KiB
Plaintext
81 lines
3.4 KiB
Plaintext
This directory contains the sources of the GNU C Library.
|
|
See the file "version.h" for what release version you have.
|
|
|
|
The GNU C Library is the standard system C library for all GNU systems,
|
|
and is an important part of what makes up a GNU system. It provides the
|
|
system API for all programs written in C and C-compatible languages such
|
|
as C++ and Objective C; the runtime facilities of other programming
|
|
languages use the C library to access the underlying operating system.
|
|
|
|
In GNU/Linux systems, the C library works with the Linux kernel to
|
|
implement the operating system behavior seen by user applications.
|
|
In GNU/Hurd systems, it works with a microkernel and Hurd servers.
|
|
|
|
The GNU C Library implements much of the POSIX.1 functionality in the
|
|
GNU/Hurd system, using configurations i[4567]86-*-gnu. The current
|
|
GNU/Hurd support requires out-of-tree patches that will eventually be
|
|
incorporated into an official GNU C Library release.
|
|
|
|
When working with Linux kernels, this version of the GNU C Library
|
|
requires Linux kernel version 2.6.16 or later.
|
|
|
|
Also note that the shared version of the libgcc_s library must be
|
|
installed for the pthread library to work correctly.
|
|
|
|
The GNU C Library supports these configurations for using Linux kernels:
|
|
|
|
i[4567]86-*-linux-gnu
|
|
x86_64-*-linux-gnu Can build either x86_64 or x32
|
|
powerpc-*-linux-gnu Hardware floating point required
|
|
powerpc64-*-linux-gnu
|
|
s390-*-linux-gnu
|
|
s390x-*-linux-gnu
|
|
sh[34]-*-linux-gnu
|
|
sparc*-*-linux-gnu
|
|
sparc64*-*-linux-gnu
|
|
|
|
The code for other CPU configurations supported by volunteers outside of
|
|
the core glibc maintenance effort is contained in the `ports' add-on,
|
|
located in the `ports' subdirectory of the source tree.
|
|
|
|
aarch64*-*-linux-gnu
|
|
alpha*-*-linux-gnu
|
|
am33*-*-linux-gnu Not currently functional
|
|
arm-*-linux-gnueabi
|
|
hppa-*-linux-gnu Not currently functional without patches.
|
|
ia64-*-linux-gnu
|
|
m68k-*-linux-gnu
|
|
mips-*-linux-gnu
|
|
mips64-*-linux-gnu
|
|
powerpc-*-linux-gnu Software floating point (--without-fp)
|
|
tilegx-*-linux-gnu
|
|
tilepro-*-linux-gnu
|
|
|
|
If you are interested in doing a port, please contact the glibc
|
|
maintainers; see http://www.gnu.org/software/libc/ for more
|
|
information.
|
|
|
|
See the file INSTALL to find out how to configure, build, and install
|
|
the GNU C Library. You might also consider reading the WWW pages for
|
|
the C library at http://www.gnu.org/software/libc/.
|
|
|
|
The GNU C Library is (almost) completely documented by the Texinfo manual
|
|
found in the `manual/' subdirectory. The manual is still being updated
|
|
and contains some known errors and omissions; we regret that we do not
|
|
have the resources to work on the manual as much as we would like. For
|
|
corrections to the manual, please file a bug in the `manual' component,
|
|
following the bug-reporting instructions below. Please be sure to check
|
|
the manual in the current development sources to see if your problem has
|
|
already been corrected.
|
|
|
|
Please see http://www.gnu.org/software/libc/bugs.html for bug reporting
|
|
information. We are now using the Bugzilla system to track all bug reports.
|
|
This web page gives detailed information on how to report bugs properly.
|
|
|
|
The GNU C Library is free software. See the file COPYING.LIB for copying
|
|
conditions, and LICENSES for notices about a few contributions that require
|
|
these additional notices to be distributed. License copyright years may be
|
|
listed using range notation, e.g., 2000-2013, indicating that every year in
|
|
the range, inclusive, is a copyrightable year that would otherwise be listed
|
|
individually.
|