This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: fixincl now run at every stage?
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: fixincl now run at every stage?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Mon, 31 Jan 2000 12:12:40 -0700
- cc: zack at wolery dot cumb dot org, autogen at linuxbox dot com, egcs-bugs at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <200001311838.NAA12263@caip.rutgers.edu>you write:
>
> Scanning recent Makefile.in changes, I'm going to hazard a guess that
> this was the culprit:
>
> > 2000-01-20 Zack Weinberg <zack@wolery.cumb.org>
> >
> > * Makefile.in (fixinc.sh): Depend on specs.
>
> Because "specs" is part of $(STAGESTUFF), We move "specs" into the
> stageN dir between stages so it gets rebuilt. Then fixinc.sh gets
> rebuilt, which triggers the stmp-fixinc target, which reruns fixinc.sh
> at every stage.
>
> It may correct this to remove "specs" from $(STAGESTUFF). But I'm not
> sure what side effect that would have.
>
> Incidentally, this problem also causes libgcc.a to be rebuilt at every
> stage due to dependencies on the header fixes.
I suspect the specs files are in STAGESTUFF so that we can find them in the
stageX directories via -BstageX/. If we don't move them, then it's likely
we won't find the spec file during the stage2/stage3 build.
libgcc does need to get rebuilt at each stage since it can contain langauge
specific stuff which wouldn't have been built during stage1.
I'm not sure how best to address this problem.
jeff
> --Kaveh
> --
> Kaveh R. Ghazi Engagement Manager / Project Services
> ghazi@caip.rutgers.edu Qwest Internet Solutions
>