This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] c++-types-check: Do not run this test if there is no C++ support
- From: Florian Weimer <fweimer at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Roland McGrath <roland at hack dot frob dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 27 Oct 2015 23:07:06 +0100
- Subject: Re: [PATCH] c++-types-check: Do not run this test if there is no C++ support
- Authentication-results: sourceware.org; auth=none
- References: <562E2784 dot 5010306 at redhat dot com> <20151027192532 dot CC8A02C3A9B at topped-with-meat dot com> <alpine dot DEB dot 2 dot 10 dot 1510272158090 dot 21730 at digraph dot polyomino dot org dot uk>
On 10/27/2015 11:00 PM, Joseph Myers wrote:
> On Tue, 27 Oct 2015, Roland McGrath wrote:
>
>> Follow the example of tst-chk4 et al in debug/Makefile. That is, just add
>> it to tests-unsupported. There is no need to conditionalize adding it to
>> tests or tests-special per se. But if it's in tests-unsupported it can't
>> have an explicit foo.out rule, so for this case conditionalizing its
>> addition to tests-special along with the explicit rule makes sense.
>
> As I understand it, tests-unsupported doesn't work at top level.
Yes, that's exactly the problem I'm running into.
> Cf <https://sourceware.org/ml/libc-alpha/2015-08/msg01284.html> and
> <https://sourceware.org/ml/libc-alpha/2015-09/msg00127.html>, where Carlos
> offered to move this test to misc/.
Thanks for the references. I'll check what can be done about this.
Florian