This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ToT build failure?
- From: Jakub Jelinek <jakub at redhat dot com>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: sellcey at cavium dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 6 Jul 2017 20:58:16 +0200
- Subject: Re: ToT build failure?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jakub at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 74CA851141
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 74CA851141
- References: <201707061705.v66H5Jv5002389@sellcey-dt.caveonetworks.com> <1499361484.7656.156.camel@redhat.com> <1499363142.7656.158.camel@redhat.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Jul 06, 2017 at 01:45:42PM -0400, David Malcolm wrote:
> Given that the previous status quo of the selftests was to require the
> C frontend, I committed the attached patch (as r250036), under the
> "obvious" rule, retaining the ability to optionally run the selftests
> within the C++ frontend.
You should do something similar for how we make check etc.:
CHECK_TARGETS = @check_languages@
check: $(CHECK_TARGETS)
and then each Make-lang.in defining its check-<lang> goal.
So similarly to that s-selftest-c++ should be in cp/Make-lang.in
and based on the configured languages should include the s-selftest-<lang>
dependencies.
Jakub