This is the mail archive of the
mailing list for the glibc project.
Re: RFC [0/2] test-in-container
Suppose /bin/sh uses a library whose system location is the same as the
location where the glibc-under-test would install something in the chroot.
(For example, say it uses /lib/libc.so.6 and the glibc-under-test would
also install that file.) Do you keep the two copies separate - keep sh's
libraries somewhere else in the chroot so the new glibc's don't overwrite
them? Even for native testing, you can't assume that the two have the
same ABI - consider various cases where hard-float and soft-float have
different ABIs but use the same library paths, for example.
What do in-container tests actually require /bin/sh to be able to do? Is
it more than just e.g. "split a command on spaces and execute it"? (I'm
wondering if a trivial /bin/sh implementation like that would suffice
inside the chroot.)
Joseph S. Myers