summaryrefslogtreecommitdiff
path: root/patches/glibc/ports-2.10.1/140-disable-ldconfig.patch
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2009-11-13 20:37:18 (GMT)
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2009-11-13 20:37:18 (GMT)
commit4b173045e97ab47f92bc27e9bef3a04f5742b263 (patch)
tree5c907ac100fc957240f4936d58c16a26554cfcdf /patches/glibc/ports-2.10.1/140-disable-ldconfig.patch
parent590ca63f0dc6a548e2254d71b065efbf38ed85d8 (diff)
libc/glibc: add 2.10.1
Woo... It seems the glibc guys finally decided that tarballs were not deprecated, in fact. The patchset was vampirised from Gentoo (kudos, guys!), and applies to glibc+ports, so that's why it's been added as a patchset against ports, not against glibc.
Diffstat (limited to 'patches/glibc/ports-2.10.1/140-disable-ldconfig.patch')
-rw-r--r--patches/glibc/ports-2.10.1/140-disable-ldconfig.patch16
1 files changed, 16 insertions, 0 deletions
diff --git a/patches/glibc/ports-2.10.1/140-disable-ldconfig.patch b/patches/glibc/ports-2.10.1/140-disable-ldconfig.patch
new file mode 100644
index 0000000..602dd10
--- /dev/null
+++ b/patches/glibc/ports-2.10.1/140-disable-ldconfig.patch
@@ -0,0 +1,16 @@
+do not bother running ldconfig on DESTDIR. it wants to write the temp cache
+file outside of the chroot. doesnt matter anyways as we wont use the cache
+results (portage will rebuild cache), so running ldconfig is simply a waste
+of time.
+
+diff -durN glibc-2.10.1.orig/Makefile glibc-2.10.1/Makefile
+--- glibc-2.10.1.orig/Makefile 2009-04-23 20:23:03.000000000 +0200
++++ glibc-2.10.1/Makefile 2009-11-13 00:49:49.000000000 +0100
+@@ -116,6 +116,7 @@
+ rm -f $(symbolic-link-list)
+
+ install:
++dont-bother-with-destdir:
+ -test ! -x $(common-objpfx)elf/ldconfig || LC_ALL=C LANGUAGE=C \
+ $(common-objpfx)elf/ldconfig $(addprefix -r ,$(install_root)) \
+ $(slibdir) $(libdir)