This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Weirdness with gcc's check-*//foo-sim rules
- From: Phil Edwards <phil at codesourcery dot com>
- To: gcc at gcc dot gnu dot org
- Cc: aoliva at redhat dot com, jsm at polyomino dot org dot uk
- Date: Wed, 7 Jul 2004 21:08:53 -0400
- Subject: Weirdness with gcc's check-*//foo-sim rules
- Reply-to: gcc at gcc dot gnu dot org
Got a surprise the other day. And it wasn't my birthday, so surprises
weren't altogether welcome. Went like this:
$ make -ik check-gcc//arm-sim/{,-mthumb} check-g++//arm-sim/{,-mthumb}
...check-gcc runs twice, in "testsuite.arm-sim." and
"testsuite.arm-sim.-mthumb" accordingly...
make[1]: Leaving directory `/path/to/objdir/gcc'
make: Nothing to be done for `check-g++//arm-sim/'.
make: Nothing to be done for `check-g++//arm-sim/-mthumb'.
$
So I've changed my local script to only ask for one check-*//foo target
a time, and now they all get run.
I'm not familiar enough with the % catch-all rules to know whether this
is even possible, so I'll ask: can this be tweaked so that invoking the
commands /once/ for the first target doesn't satisfy the deps for all the
other targets derived from the same rule?
If not, I'll just document this limitation on the testing pages.
Phil
--
<The_Vulture> evilgeek: actually it's <: and :>, <% and %>
<evilgeek> oh, right. digraphs are always happy