aboutsummaryrefslogtreecommitdiff
path: root/Makeconfig
diff options
context:
space:
mode:
authorStephanie J. Lockwood-Childs <wormo@gentoo.org>2013-08-16 15:03:41 -0400
committerMike Frysinger <vapier@gentoo.org>2015-08-05 06:44:54 -0400
commit016376847a12b35e43cd82d6964451b3d391b8ed (patch)
tree48d17bc1feed6b86d3c208a6e9b0b9dcc8429392 /Makeconfig
parente973063f44ce67dd737e88765afb024a06fca847 (diff)
downloadglibc-016376847a12b35e43cd82d6964451b3d391b8ed.tar
glibc-016376847a12b35e43cd82d6964451b3d391b8ed.tar.gz
glibc-016376847a12b35e43cd82d6964451b3d391b8ed.tar.bz2
glibc-016376847a12b35e43cd82d6964451b3d391b8ed.zip
gentoo: support running tests under sandbox
when glibc runs its tests, it does so by invoking the local library loader. in Gentoo, we build/run inside of our "sandbox" which itself is linked against libdl (so that it can load libraries and pull out symbols). the trouble is that when you upgrade from an older glibc to the new one, often times internal symbols change name or abi. this is normally OK as you cannot use libc.so from say version 2.3.6 but libpthread.so from say version 2.5, so we always say "keep all of the glibc libraries from the same build". but when glibc runs its tests, it uses dynamic paths to point to its new local copies of libraries. if the test doesnt use libdl, then glibc doesnt add its path, and when sandbox triggers the loading of libdl, glibc does so from the host system system. this gets us into the case of all libraries are from the locally compiled version of glibc except for libdl.so. http://bugs.gentoo.org/56898
Diffstat (limited to 'Makeconfig')
-rw-r--r--Makeconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makeconfig b/Makeconfig
index f136b88da1..0dbcafd179 100644
--- a/Makeconfig
+++ b/Makeconfig
@@ -648,7 +648,7 @@ comma = ,
sysdep-library-path = \
$(subst $(empty) ,:,$(strip $(patsubst -Wl$(comma)-rpath-link=%, %,\
$(filter -Wl$(comma)-rpath-link=%,\
- $(sysdep-LDFLAGS)))))
+ $(sysdep-LDFLAGS)))) $(common-objpfx)/dlfcn)
# $(run-via-rtld-prefix) is a command that, when prepended to the name
# of a program built with the newly built library, produces a command
# that, executed on the host for which the library is built, runs that