aboutsummaryrefslogtreecommitdiff
path: root/ports/README
diff options
context:
space:
mode:
authorJoseph Myers <joseph@codesourcery.com>2012-07-01 13:06:41 +0000
committerJoseph Myers <joseph@codesourcery.com>2012-07-01 13:06:41 +0000
commite64ac02c24b43659048622714afdc92fedf561fa (patch)
tree37162878b72d302de351788bec4c9360c9d55f1d /ports/README
parenta20c2b3c87aebc7d4b090c622d36480263b80042 (diff)
downloadglibc-e64ac02c24b43659048622714afdc92fedf561fa.zip
glibc-e64ac02c24b43659048622714afdc92fedf561fa.tar.gz
glibc-e64ac02c24b43659048622714afdc92fedf561fa.tar.bz2
Move all files into ports/ subdirectory in preparation for merge with glibcglibc-2.16-ports-before-merge
Diffstat (limited to 'ports/README')
-rw-r--r--ports/README50
1 files changed, 50 insertions, 0 deletions
diff --git a/ports/README b/ports/README
new file mode 100644
index 0000000..51e0a30
--- /dev/null
+++ b/ports/README
@@ -0,0 +1,50 @@
+This is the glibc ports repository, 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
+are not maintained in the official glibc source tree. It also includes
+some code once used by old libc ports now defunct, which has been abandoned
+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
+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
+README and Banner of your own talking about your port's code in particular,
+rather than the generic ones here.
+
+The real source code for any ports is found in the sysdeps/ subdirectories.
+These should be exactly what would go into the main libc source tree if you
+were to incorporate it directly. The only exceptions are the files
+sysdeps/*/preconfigure and sysdeps/*/preconfigure.in; these are fragments
+used by this add-on's configure fragment. The purpose of these is to set
+$base_machine et al when the main libc configure's defaults are not right
+for some machine. Everything else can and should be done from a normal
+sysdeps/.../configure fragment that is used only when the configuration
+selects that sysdeps subdirectory. Each port that requires some special
+treatment before the sysdeps directory list is calculated, should add a
+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.
+
+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 GNU C Library is free software. See the file COPYING.LIB in the
+libc repository 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-2011, indicating that every year in the range,
+inclusive, is a copyrightable year that would otherwise be listed
+individually.