From: | arnold@skeeve.com |
Newsgroups: | comp.compilers |
Date: | Thu, 29 Sep 2016 05:30:57 -0600 |
Organization: | Compilers Central |
References: | 16-09-001 16-09-033 16-09-034 <b5cdb632-7a67-d577-102d-1a1e23d062f7@gkc.org.uk> |
Injection-Info: | miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="95651"; mail-complaints-to="abuse@iecc.com" |
Keywords: | C, practice |
Posted-Date: | 29 Sep 2016 21:34:58 EDT |
> The whole point of "make" is to avoid recompiling things that
> do not need to be recompiled. By repeatedly doing "make distclean"
> you are circumventing this system.
>
> Find out why make is not compiling everything that it needs to.
I am purposely cleaning up the directory so that builds occur from
scratch as I *** switch between branches *** in the git repo. Especially on
the 'stable' and 'master' branches I have to be sure that anyone
checking out those branches will have things work for them.
I am thinking this discussion has gotten out of hand and I apologize
for it. All I'm looking for is a fast compiler for development
since I on purpose do a lot of configure + make from scratch.
I don't care about code quality; just that 'make check' passes.
Since posting, I have repaired tcc to the point where I can use it,
so I'm happy. The PCC issue remains to be resolved; gawk's code changed
(the dfa module from grep) and PCC stopped working. I will eventually
go to the trouble of isolating the problem but it's probably a few
hours' work and that's time I don't have right now.
Thanks to everyone for their replies.
Arnold
Return to the
comp.compilers page.
Search the
comp.compilers archives again.