pruning worthless glibc patches from CT-ng

["Robert P. J. Day" <rpjday at crashcourse dot ca>]

  as a quick way to get rid of some utter deadwood from crosstool-ng
(and crosstool itself, for that matter), it would be nice to toss some
of the patches that have been carried forward since god only knows
when.

  currently, if you check the patch sets for glibc that are currently
in CT-ng, you see:

$ cd patches/glibc
$ find 2.3.6 2.5 2.5.1 2.6 2.6.1 -name *patch

2.3.6/240-weakalias.patch
2.3.6/100-arm-ctl_bus_isa.patch
2.3.6/maybe/glibc-2.3.6-allow-gcc-4.0-powerpc64.patch
2.3.6/maybe/glibc-2.3.6-allow-gcc-4.0-powerpc32.patch
2.3.6/180-glibc-2.3.6-allow-gcc-4.0-elf.patch
2.3.6/140-glibc-2.3.5-cygwin.patch
2.3.6/130-glibc-2.3.5-allow-gcc4-wcstol_l.patch
2.3.6/160-glibc-2.3.5-sh-memset.patch
2.3.6/120-glibc-2.3.5-allow-gcc-4.0-wordexp.patch
2.3.6/190-glibc-2.3.6-configure-apple-as.patch
2.3.6/210-glibc-fp-byteorder.patch
2.3.6/110-fix-pr398.patch
2.3.6/220-glibc-mips-bootstrap-gcc-header-install.patch
2.3.6/200-glibc-2.3.6-fix-pr631.patch
2.3.6/150-glibc-2.3.5-sh-lowlevellock.patch
2.3.6/170-glibc-2.3.6-allow-gcc-4.0-arm.patch
2.3.6/230-make-install-lib-all.patch

2.5/160-glibc-2.4-i686-assembler.patch
2.5/150-glibc-2.3.6-fix-pr631.patch
2.5/130-glibc-2.3.6-allow-gcc-4.0-elf.patch
2.5/140-glibc-2.3.6-configure-apple-as.patch
2.5/170-glibc-i386-preferred-stack-boundary.patch
2.5/110-glibc-2.3.5-allow-gcc4-wcstol_l.patch
2.5/120-glibc-2.3.5-cygwin.patch

2.5.1/160-glibc-2.4-i686-assembler.patch
2.5.1/150-glibc-2.3.6-fix-pr631.patch
2.5.1/130-glibc-2.3.6-allow-gcc-4.0-elf.patch
2.5.1/140-glibc-2.3.6-configure-apple-as.patch
2.5.1/170-glibc-i386-preferred-stack-boundary.patch
2.5.1/110-glibc-2.3.5-allow-gcc4-wcstol_l.patch
2.5.1/120-glibc-2.3.5-cygwin.patch

2.6/160-glibc-2.4-i686-assembler.patch
2.6/150-glibc-2.3.6-fix-pr631.patch
2.6/130-glibc-2.3.6-allow-gcc-4.0-elf.patch
2.6/140-glibc-2.3.6-configure-apple-as.patch
2.6/170-glibc-i386-preferred-stack-boundary.patch
2.6/110-glibc-2.3.5-allow-gcc4-wcstol_l.patch
2.6/120-glibc-2.3.5-cygwin.patch

2.6.1/160-glibc-2.4-i686-assembler.patch
2.6.1/150-glibc-2.3.6-fix-pr631.patch
2.6.1/130-glibc-2.3.6-allow-gcc-4.0-elf.patch
2.6.1/140-glibc-2.3.6-configure-apple-as.patch
2.6.1/170-glibc-i386-preferred-stack-boundary.patch
2.6.1/110-glibc-2.3.5-allow-gcc4-wcstol_l.patch
2.6.1/120-glibc-2.3.5-cygwin.patch
$

  it seems fairly clear that a lot of very old patches have been
carried forward as long as they continued to apply, even if they had
no value anymore.  if you're feeling ambitious, take a look at those
later patchsets and see which patches no longer serve any useful
purpose and can be scrapped.

  once that's done, it should be easier to develop the necessary
patchset for glibc-2.7 (also what should be a quick and dirty
project).

  thoughts?

rday

p.s.  clearly, the same ruthless pruning could be applied to any of
the *other* software components in CT-ng, such as gcc, gdb, etc.

--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

--
For unsubscribe information see http://sourceware.org/lists.html#faq