COPYING
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Feb 02 22:00:18 2009 +0000 (2009-02-02)
changeset 1201 c9967a6e3b25
parent 676 78c450c0b219
permissions -rw-r--r--
Add a patchset for glibc 2_9. Vampirised from the gentoo repository.

/trunk/patches/glibc/2_9/500-ppc-glibc-2.9-atomic.patch | 414 414 0 0 ++++++++++
/trunk/patches/glibc/2_9/140-regex-BZ9697.patch | 111 111 0 0 +++
/trunk/patches/glibc/2_9/190-queue-header-updates.patch | 89 89 0 0 ++
/trunk/patches/glibc/2_9/370-hppa_glibc-2.7-hppa-nptl-carlos.patch | 249 249 0 0 ++++++
/trunk/patches/glibc/2_9/450-alpha-glibc-2.5-no-page-header.patch | 32 32 0 0 +
/trunk/patches/glibc/2_9/270-ldbl-nexttowardf.patch | 68 68 0 0 ++
/trunk/patches/glibc/2_9/330-2.3.3-china.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/340-new-valencian-locale.patch | 120 120 0 0 +++
/trunk/patches/glibc/2_9/410-2.9-fnmatch.patch | 64 64 0 0 ++
/trunk/patches/glibc/2_9/350-2.4-undefine-__i686.patch | 47 47 0 0 +
/trunk/patches/glibc/2_9/160-i386-x86_64-revert-clone-cfi.patch | 53 53 0 0 +
/trunk/patches/glibc/2_9/420-dont-build-timezone.patch | 19 19 0 0 +
/trunk/patches/glibc/2_9/150-regex-BZ697.patch | 28 28 0 0 +
/trunk/patches/glibc/2_9/290-no-inline-gmon.patch | 38 38 0 0 +
/trunk/patches/glibc/2_9/280-section-comments.patch | 29 29 0 0 +
/trunk/patches/glibc/2_9/180-math-tests.patch | 72 72 0 0 ++
/trunk/patches/glibc/2_9/120-_nss_dns_gethostbyaddr2_r-check-and-adjust-the-buffer-alignment.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/250-resolv-dynamic.patch | 44 44 0 0 +
/trunk/patches/glibc/2_9/300-2.9-check_native-headers.patch | 22 22 0 0 +
/trunk/patches/glibc/2_9/310-2.3.6-fix-pr631.patch | 50 50 0 0 +
/trunk/patches/glibc/2_9/130-add_prio-macros.patch | 26 26 0 0 +
/trunk/patches/glibc/2_9/260-fadvise64_64.patch | 30 30 0 0 +
/trunk/patches/glibc/2_9/440-alpha-glibc-2.4-xstat.patch | 249 249 0 0 ++++++
/trunk/patches/glibc/2_9/170-2.10-dns-no-gethostbyname4.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/230-2.3.3-localedef-fix-trampoline.patch | 74 74 0 0 ++
/trunk/patches/glibc/2_9/360-2.8-nscd-one-fork.patch | 45 45 0 0 +
/trunk/patches/glibc/2_9/480-alpha-glibc-2.8-cache-shape.patch | 18 18 0 0 +
/trunk/patches/glibc/2_9/210-2.9-strlen-hack.patch | 109 109 0 0 +++
/trunk/patches/glibc/2_9/320-2.9-assume-pipe2.patch | 59 59 0 0 +
/trunk/patches/glibc/2_9/100-ssp-compat.patch | 193 193 0 0 +++++
/trunk/patches/glibc/2_9/110-respect-env-CPPFLAGS.patch | 30 30 0 0 +
/trunk/patches/glibc/2_9/220-manual-no-perl.patch | 29 29 0 0 +
/trunk/patches/glibc/2_9/390-2.3.3_pre20040117-pt_pax.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/460-alpha-glibc-2.5-no-asm-elf-header.patch | 38 38 0 0 +
/trunk/patches/glibc/2_9/400-tests-sandbox-libdl-paths.patch | 198 198 0 0 +++++
/trunk/patches/glibc/2_9/240-i386-LOAD_PIC_REG.patch | 23 23 0 0 +
/trunk/patches/glibc/2_9/200-awk-in-C-locale.patch | 23 23 0 0 +
/trunk/patches/glibc/2_9/430-2.7-cross-compile-nptl.patch | 57 57 0 0 +
/trunk/patches/glibc/2_9/380-2.3.6-dl_execstack-PaX-support.patch | 71 71 0 0 ++
/trunk/patches/glibc/2_9/490-ptr-mangling.patch | 114 114 0 0 +++
/trunk/patches/glibc/2_9/470-alpha-glibc-2.8-creat.patch | 19 19 0 0 +
41 files changed, 3094 insertions(+)
yann@425
     1
Unless otherwise stated in individual files, this work is licensed to you under
yann@1
     2
the following terms.
yann@1
     3
yann@1
     4
- Files in docs/ are available under the Creative Commons Attribution, Share
yann@1
     5
  Alike (by-sa), v2.5, to be found there:
yann@17
     6
    licenses.d/by-sa/deed.en     (human-readable summary)
yann@17
     7
    licenses.d/by-sa/legalcode   (legal code, the full license)
yann@1
     8
    
yann@191
     9
- Files found in patches/*/ are available under the same license as the
yann@338
    10
  upstream software they apply to.
yann@338
    11
yann@338
    12
  That means that you can't use those patches if you were licensed the
yann@338
    13
  software under a specific license which is not the one the software is
yann@338
    14
  commonly available under.
yann@338
    15
yann@338
    16
  As an example, if you ever managed to get the Linux kernel under a license
yann@338
    17
  other than the GPLv2, you are not allowed to use the Linux kernel patches
yann@338
    18
  coming with crosstool-NG, as those are available under the GPLv2, which is
yann@338
    19
  the license the Linux kernel is most commonly available under.
yann@338
    20
yann@338
    21
  As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the
yann@853
    22
  patches against glibc, uClibc, and some other libraries) is available there:
yann@338
    23
    licenses.d/lgpl.txt
yann@1
    24
yann@1
    25
- Other files not covered by the above licenses, and not covered by an
yann@1
    26
  individual license specified in the file itself, or an accompanying file,
yann@1
    27
  are available under the GNU General Public License (GPL), v2, to be found
yann@1
    28
  here:
yann@17
    29
    licenses.d/gpl.txt
yann@676
    30
yann@676
    31
- Also, I want to clarify one point. If you build a toolchain with crosstool-NG
yann@676
    32
  and you happen to sell, deliver, or otherwise publish this toolchain to a
yann@676
    33
  third party, I consider crosstool-NG as being part of the sources needed to
yann@676
    34
  rebuild the afore-mentioned toolchain, alongside with all other source code
yann@676
    35
  that third party is otherwise entitled to receive, due to other licenses of
yann@676
    36
  the different components. See licenses.d/gpl.txt, section 3, which reads:
yann@676
    37
   > For an executable work, complete source code means [...], plus the
yann@676
    38
   > scripts used to control compilation and installation of the executable.
yann@676
    39
yann@676
    40
  In short: crosstool-NG is the part refered to as "the scripts to control
yann@853
    41
  compilation and installation of the executable", it being the toolchain in
yann@676
    42
  our case; and as such you must make it available, in conformance to the
yann@676
    43
  GPLv2, see above.
yann@853
    44
yann@853
    45
  Also, if you have local patches that you apply to the different components
yann@853
    46
  (either manualy, or by instructing crosstool-NG to do so), you will have to
yann@853
    47
  make those patches available alongside with your toolchain, to comply with
yann@853
    48
  the licenses of the components impacted by your patches.