From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org
Subject: Re: RFC: test-in-container vs ld.so
Date: Fri, 08 Nov 2019 03:05:30 -0500 [thread overview]
Message-ID: <xn7e4ardx1.fsf@greed.delorie.com> (raw)
In-Reply-To: <87wocavneb.fsf@mid.deneb.enyo.de> (message from Florian Weimer on Fri, 08 Nov 2019 08:27:08 +0100)
Florian Weimer <fw@deneb.enyo.de> writes:
> But I think we are already doing that? test-container is run via
> ld.so, but the actual test is not?
>
Here's nss/tst-nss-test3, with some newlines and tabs added for readability:
env GCONV_PATH=/envy/dj/tools/upstream/glibc.pristine.build/iconvdata
LOCPATH=/envy/dj/tools/upstream/glibc.pristine.build/localedata LC_ALL=C
/envy/dj/tools/upstream/glibc.pristine.build/elf/ld-linux-x86-64.so.2
--library-path
/envy/dj/tools/upstream/glibc.pristine.build:/envy/dj/tools/upstream/glibc.pristine.build/math:/envy/dj/tools/upstream/glibc.pristine.build/elf:/envy/dj/tools/upstream/glibc.pristine.build/dlfcn:/envy/dj/tools/upstream/glibc.pristine.build/nss:/envy/dj/tools/upstream/glibc.pristine.build/nis:/envy/dj/tools/upstream/glibc.pristine.build/rt:/envy/dj/tools/upstream/glibc.pristine.build/resolv:/envy/dj/tools/upstream/glibc.pristine.build/mathvec:/envy/dj/tools/upstream/glibc.pristine.build/support:/envy/dj/tools/upstream/glibc.pristine.build/crypt:/envy/dj/tools/upstream/glibc.pristine.build/nptl
\
/envy/dj/tools/upstream/glibc.pristine.build/support/test-container
env GCONV_PATH=/envy/dj/tools/upstream/glibc.pristine.build/iconvdata
LOCPATH=/envy/dj/tools/upstream/glibc.pristine.build/localedata
LC_ALL=C \
/envy/dj/tools/upstream/glibc.pristine.build/elf/ld-linux-x86-64.so.2
--library-path
/envy/dj/tools/upstream/glibc.pristine.build:/envy/dj/tools/upstream/glibc.pristine.build/math:/envy/dj/tools/upstream/glibc.pristine.build/elf:/envy/dj/tools/upstream/glibc.pristine.build/dlfcn:/envy/dj/tools/upstream/glibc.pristine.build/nss:/envy/dj/tools/upstream/glibc.pristine.build/nis:/envy/dj/tools/upstream/glibc.pristine.build/rt:/envy/dj/tools/upstream/glibc.pristine.build/resolv:/envy/dj/tools/upstream/glibc.pristine.build/mathvec:/envy/dj/tools/upstream/glibc.pristine.build/support:/envy/dj/tools/upstream/glibc.pristine.build/crypt:/envy/dj/tools/upstream/glibc.pristine.build/nptl \
/envy/dj/tools/upstream/glibc.pristine.build/nss/tst-nss-test3 >
/envy/dj/tools/upstream/glibc.pristine.build/nss/tst-nss-test3.out
next prev parent reply other threads:[~2019-11-08 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 22:31 RFC: test-in-container vs ld.so DJ Delorie
2019-11-08 7:27 ` Florian Weimer
2019-11-08 8:05 ` DJ Delorie [this message]
2019-11-08 8:25 ` Florian Weimer
2019-11-08 23:54 ` DJ Delorie
2019-11-09 13:24 ` Carlos O'Donell
2019-11-09 14:05 ` Florian Weimer
2019-12-06 4:19 ` DJ Delorie
2019-12-06 20:09 ` DJ Delorie
2019-12-10 19:33 ` Carlos O'Donell
2019-12-10 19:37 ` DJ Delorie
2019-11-08 15:07 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xn7e4ardx1.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).