[PATCH] Add --enable-dynamic-test configure option

[Carlos O'Donell]

On 12/10/2012 08:36 AM, Nix wrote:
> 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.)

In general most applications aren't built with DT_RPATH, and by
making this the default we would be a little further from the
behaviour of normal applications.

I think it's a great idea to add this feature for developers
who are building/debugging glibc tests since in that case it
saves you rebuilding the test case for easy debug under gdb.

In summary: Cool new feature. Shouldn't be default.

Looking into the future I can see a time when we run the glibc
testsuite in a minimal chroot built by the glibc build process.

The higher the fidelty of the testing environment the more
things we can test reliably.

Cheers,
Carlos.