What happens if the dependency on TPIKE_TARGETS is simply removed? All other initial Pike dependencies can be solved by using the system Pike, why not dependency creation?
One way to solve it is to include the dependency files in CVS. That way they will get updated when CVS is updated.
force_autoconfig or force_configure doesn't clear dependencies what I can see? I reran autoconfig and configure (manually) before I got caught in the catch 22.
/ Mirar
Previous text:
2003-01-05 22:38: Subject: depend
Make cvsclean to get rid of them. And yes, the tpike stuff is a leftover from before there were cmods etc that need a pike to build the pike core (from cvs). It isn't useful anymore and could be cleaned up.
I don't understand how you think it could be solved. There are many other situations where you get similar brokeness which a simple remake doesn't handle, e.g. when a new module directory is added, or when a module Makefile is incorrectly made by a direct configure so that it loses PIKE_SRC_DIR and BUILD_BASE. The recipe in all these cases is to run a sufficiently thorough clean target or remake from a point sufficiently early in the build process (make force_configure or force_autoconfig).
/ Martin Stjernholm, Roxen IS