This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Ports-related README updates


The main and ports README files are in need of updates to reflect that 
ports no longer uses a separate repository or release tarballs.  This 
patch attempts to make such updates.  It also adds AArch64 to the list in 
README of ports architectures.  A reference to scripts/data/ in the ports 
README is removed, since all such files have now moved to sysdeps 
directories.

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.

ports/ChangeLog:
2012-12-05  Joseph Myers  <joseph@codesourcery.com>

	* README: Don't refer to ports as a separate repository.  Don't
	refer to scripts/data/.

diff --git a/README b/README
index 1d90b55..b34d5c0 100644
--- a/README
+++ b/README
@@ -35,11 +35,10 @@ The GNU C Library supports these configurations for using Linux kernels:
 	sparc64*-*-linux-gnu
 
 The code for other CPU configurations supported by volunteers outside of
-the core glibc maintenance effort is contained in the separate `ports'
-add-on.  You can find glibc-ports-VERSION distributed separately in the
-same place where you got the main glibc distribution files.
-Currently these configurations have code in the `ports' add-on:
+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
diff --git a/ports/README b/ports/README
index 51e0a30..7c27ccc 100644
--- a/ports/README
+++ b/ports/README
@@ -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.
 
 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
 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 a separate
-ports git repository.  See
+The ports add-on is cooperatively maintained by volunteers on the
+<libc-ports@sourceware.org> mailing list, and housed in the ports
+subdirectory of the glibc 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.
+git.  To report a bug in code housed in the ports add-on, 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
@@ -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
 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.  Files that
-would go in scripts/data/ for libc go in data/ in ports.
+into a single add-on without interfering with each other.
 
 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.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]