Update ports README file.

This commit is contained in:
Joseph Myers 2012-02-07 12:56:48 +00:00
parent e1102f7294
commit b3c737fd39
2 changed files with 12 additions and 6 deletions

View File

@ -1,3 +1,7 @@
2012-02-07 Joseph Myers <joseph@codesourcery.com>
* README: Update.
2012-02-07 Joseph Myers <joseph@codesourcery.com> 2012-02-07 Joseph Myers <joseph@codesourcery.com>
* README: Document use of ranges in copyright notices. * README: Document use of ranges in copyright notices.

14
README
View File

@ -9,11 +9,12 @@ 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 repository is cooperatively maintained by volunteers on the
<libc-ports@sourceware.org> mailing list, and housed in the glibc CVS as a <libc-ports@sourceware.org> mailing list, and housed in a separate
module called "ports". See http://www.gnu.org/software/libc/resources.html ports git repository. See
for details on using CVS. To report a bug in code housed in the ports http://www.gnu.org/software/libc/download.html for details on using
repository, please go to http://sources.redhat.com/bugzilla/ and file a bug git. To report a bug in code housed in the ports repository, please
report under the glibc "ports" component. go to http://sources.redhat.com/bugzilla/ and file a bug report under
the 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
@ -34,7 +35,8 @@ 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. into a single add-on without interfering with each other. Files that
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.