aboutsummaryrefslogtreecommitdiff
path: root/posix
diff options
context:
space:
mode:
authorStephanie J. Lockwood-Childs <wormo@gentoo.org>2007-03-13 01:57:21 -0400
committerMike Frysinger <vapier@gentoo.org>2016-11-11 15:18:47 -0500
commit9886b16ac4268e98cec9f70b1ba1e7136eb56da5 (patch)
treed2cc4351e310ec2075ff340c75674eb680281af1 /posix
parent0b97118e38a9fe9facbe1e2178a32790b655ee5c (diff)
downloadglibc-9886b16ac4268e98cec9f70b1ba1e7136eb56da5.zip
glibc-9886b16ac4268e98cec9f70b1ba1e7136eb56da5.tar.gz
glibc-9886b16ac4268e98cec9f70b1ba1e7136eb56da5.tar.bz2
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 'posix')
0 files changed, 0 insertions, 0 deletions