Ports-related README updates.

This commit is contained in:
Joseph Myers 2012-12-05 22:15:52 +00:00
parent 8760036569
commit effbd42a77
4 changed files with 17 additions and 13 deletions

View File

@ -1,5 +1,8 @@
2012-12-05 Joseph Myers <joseph@codesourcery.com> 2012-12-05 Joseph Myers <joseph@codesourcery.com>
* README: Don't refer to ports add-on as distributed separately.
Mention AArch64 in list of systems supported in the ports add-on.
* LICENSES: Add more non-FSF copyright and license notices. * LICENSES: Add more non-FSF copyright and license notices.
* soft-fp/op-common.h (_FP_DECL): Declare X##_s with __attribute__ * soft-fp/op-common.h (_FP_DECL): Declare X##_s with __attribute__

7
README
View File

@ -35,11 +35,10 @@ The GNU C Library supports these configurations for using Linux kernels:
sparc64*-*-linux-gnu sparc64*-*-linux-gnu
The code for other CPU configurations supported by volunteers outside of The code for other CPU configurations supported by volunteers outside of
the core glibc maintenance effort is contained in the separate `ports' the core glibc maintenance effort is contained in the `ports' add-on,
add-on. You can find glibc-ports-VERSION distributed separately in the located in the `ports' subdirectory of the source tree.
same place where you got the main glibc distribution files.
Currently these configurations have code in the `ports' add-on:
aarch64*-*-linux-gnu
alpha*-*-linux-gnu alpha*-*-linux-gnu
am33*-*-linux-gnu Not currently functional am33*-*-linux-gnu Not currently functional
arm-*-linux-gnueabi arm-*-linux-gnueabi

View File

@ -1,5 +1,8 @@
2012-07-03 Joseph Myers <joseph@codesourcery.com> 2012-07-03 Joseph Myers <joseph@codesourcery.com>
* README: Don't refer to ports as a separate repository. Don't
refer to scripts/data/.
* .gitignore: Remove file. * .gitignore: Remove file.
* Banner: Likewise. * Banner: Likewise.
* Makefile: Likewise. * Makefile: Likewise.

View File

@ -1,4 +1,4 @@
This is the glibc ports repository, an add-on for the GNU C Library (glibc). This is the glibc ports add-on, an add-on for the GNU C Library (glibc).
It contains code that is not maintained in the official glibc source tree. It contains code that is not maintained in the official glibc source tree.
This includes working ports to GNU/Linux on some machine architectures that This includes working ports to GNU/Linux on some machine architectures that
@ -8,13 +8,13 @@ but may be useful for some future porter to examine. It may also include
some optimized functions tailored for specific CPU implementations of an some optimized functions tailored for specific CPU implementations of an
architecture, to be selected using --with-cpu. architecture, to be selected using --with-cpu.
The ports repository is cooperatively maintained by volunteers on the The ports add-on is cooperatively maintained by volunteers on the
<libc-ports@sourceware.org> mailing list, and housed in a separate <libc-ports@sourceware.org> mailing list, and housed in the ports
ports git repository. See subdirectory of the glibc git repository. See
http://www.gnu.org/software/libc/download.html for details on using http://www.gnu.org/software/libc/download.html for details on using
git. To report a bug in code housed in the ports repository, please git. To report a bug in code housed in the ports add-on, please go to
go to http://sources.redhat.com/bugzilla/ and file a bug report under http://sources.redhat.com/bugzilla/ and file a bug report under the
the glibc "ports" component. glibc "ports" component.
An add-on for an individual port can be made from just the sysdeps/ An add-on for an individual port can be made from just the sysdeps/
subdirectories containing the port's code. You may want to include a subdirectories containing the port's code. You may want to include a
@ -35,8 +35,7 @@ sysdeps/CPU/preconfigure file; this can either be written by hand or
generated by Autoconf from sysdeps/CPU/preconfigure.in, and follow the generated by Autoconf from sysdeps/CPU/preconfigure.in, and follow the
rules for glibc add-on configure fragments. No preconfigure file should do rules for glibc add-on configure fragments. No preconfigure file should do
anything on an unrelated configuration, so that disparate ports can be put anything on an unrelated configuration, so that disparate ports can be put
into a single add-on without interfering with each other. Files that into a single add-on without interfering with each other.
would go in scripts/data/ for libc go in data/ in ports.
Like all glibc add-ons, this must be used by specifying the directory in Like all glibc add-ons, this must be used by specifying the directory in
the --enable-add-ons option when running glibc's configure script. the --enable-add-ons option when running glibc's configure script.