This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC V4 test-in-container
- From: Joseph Myers <joseph at codesourcery dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: <fweimer at redhat dot com>, <libc-alpha at sourceware dot org>
- Date: Fri, 29 Jun 2018 17:42:58 +0000
- Subject: Re: RFC V4 test-in-container
- References: <xn1scph8kn.fsf@greed.delorie.com>
On Fri, 29 Jun 2018, DJ Delorie wrote:
>
> Joseph Myers <joseph@codesourcery.com> writes:
> > I remain concerned about copying /bin/sh rather than having a local
> > sh-substitute. Can using the newly built dynamic linker to trace what's
> > required by /bin/sh really work even in as simple a case as testing i386
> > glibc on an x86_64 system, where /bin/sh is a 64-bit binary?
>
> I can write a /bin/sh substitute as long as none of our tests test *it*
> and not just the calls that require it ;-)
I think that's the right thing to do - avoid any dependence on host
binaries or libraries beyond the libgcc_s / libstdc++ etc. shared
libraries, *for the ABI for which glibc is built*, on which the compiler
automatically introduces dependencies.
--
Joseph S. Myers
joseph@codesourcery.com