This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: At last: the bool problem seems to be due to omitted dependencyfrom make check*
- From: Michael S. Zick <mszick at goquest dot com>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>,Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Mon, 3 Mar 2003 07:38:58 -0600
- Subject: Re: At last: the bool problem seems to be due to omitted dependencyfrom make check*
- References: <Pine.LNX.4.33.0303030911030.29421-100000@kern.srcf.societies.cam.ac.uk>
- Reply-to: mszick at goquest dot com
On Monday 03 March 2003 03:13 am, Joseph S. Myers wrote:
> On Mon, 3 Mar 2003, Fergus Henderson wrote:
> > > Both problems should be solved, but the dependency one is intrinsically
> > > hard to solve. After all, if you change toplev.c, it should first
> > > rebuild to stage1 toplev.o with the bootstrap compiler, then relink the
> > > stage1 compiler, then rebuild stage2 and stage3, if the dependencies
> > > are properly correct.
> >
> > Isn't that what "make bubblestrap" is for?
>
> Perhaps then that's what the testsuite rules should depend on to fix the
> immediate problem, but ideally you wouldn't need special rules like that;
> the testsuite rules would just depend on "all" (compiler and libraries
> built) which would depend on the specific executables and libraries used,
> and the rules and dependencies would handle the bootstrap automatically
> without the need for moving files around.
Perhaps a RFA for the testsuite...
Is there a way to put notations into each testsuite test entry that:
1) to the testsuite look like comments (no effect on tests)
2) lists the source files that where touched when the problem a
test is checking for was (last) corrected.
This would provide a lead into finding the problem when that
test begins to fail in the future.
Mike