This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Add --enable-dynamic-test configure option
- From: Nix <nix at esperi dot org dot uk>
- To: Andi Kleen <andi at firstfloor dot org>
- Cc: Andreas Schwab <schwab at linux-m68k dot org>, "H.J. Lu" <hjl dot tools at gmail dot com>, Roland McGrath <roland at hack dot frob dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 10 Dec 2012 13:36:31 +0000
- Subject: Re: [PATCH] Add --enable-dynamic-test configure option
- References: <20121009124954.GA30448@gmail.com><20121011000517.F33FA2C06C@topped-with-meat.com><m27gqxmpta.fsf@igel.home><20121011222012.5DD132C0C2@topped-with-meat.com><20121208233610.GA22759@gmail.com> <m2fw3f77w8.fsf@igel.home><m238zff150.fsf@firstfloor.org>
On 9 Dec 2012, Andi Kleen told this:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> "H.J. Lu" <hjl.tools@gmail.com> writes:
>>
>>> Here is the updated patch to add --enable-dynamic-test.
>>
>> That's a pretty non-descriptive option name.
>>
>> --enable-hardcode-build-in-tests
>
> Or just make it default without option.
>
> When you you ever not want to do that?
When you want to compare the behaviour of a test with an old and new C
library, or with multiple C library build trees with different changes
applied to each.
(Sure, the former is obscure becaue the old C library would hopefully
have passed the tests, but I've done the latter a few times. It's hardly
killingly useful, though, because multiple build trees are going to have
multiple copies of the test programs in them as well. On balance, I
agree, this option should be on by default.)
--
NULL && (void)