mirror/glibc
2
0
Fork 0
mirror of git://sourceware.org/git/glibc.git synced 2025-02-23 13:09:58 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update ports README file.

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,3 +1,7 @@
2012-02-07 Joseph Myers <joseph@codesourcery.com>
* README: Update.
2012-02-07 Joseph Myers <joseph@codesourcery.com>
* 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.
The ports repository is cooperatively maintained by volunteers on the
<libc-ports@sourceware.org> mailing list, and housed in the glibc CVS as a
module called "ports". See http://www.gnu.org/software/libc/resources.html
for details on using CVS. To report a bug in code housed in the ports
repository, please go to http://sources.redhat.com/bugzilla/ and file a bug
report under the glibc "ports" component.
<libc-ports@sourceware.org> mailing list, and housed in a separate
ports git repository. See
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
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/
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
rules for glibc add-on configure fragments. No preconfigure file should do
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
the --enable-add-ons option when running glibc's configure script.