I see how I've gotten myself into this mess then. I originally imported gforth into my CVS repository without any concern for file order. Therefore, when doing a clean checkout, prim is checked out before engine/prim.i, which, as I write this, should have been ok, but there must be some other dependency that has always been making this happen.
So, I'll do some experiments with BUILD-FROM-SCRATCH and maybe some touches might work. Since I'm only concerned with this in a first run situation, I know there's a solution. It's just figuring it out that is frustrating. DaR > -----Original Message----- > From: Anton Ertl [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 03, 2003 8:48 AM > To: [EMAIL PROTECTED] > Subject: Re: [gforth] New snapshot available > > > Dennis Ruffer wrote: > > > > The autoconf version is certainly suspect, since I have > 2.53a on cygwin and > > 2.52 on OSX, but it's more curious that your distribution > works fine and my > > CVS repository does not. The only difference is the file > creation dates, > > which means I should be able to break your distribution by > touching some > > file(s) before configuring/making it. > > Yes, the distribution supplies a working configure script, so you > don't need autoconf to use the files as distributed. Only if you > touch configure.in, autoconf is needed. > > Similarly, the distribution supplies a working engine/prim.i (etc.), > so you don't need gforth to build it from the distribution. But if > you touch prim, or any other prerequisite of engine/prim.i, you do > need a working gforth to rebuild it. > > If you check in just the real source files (i.e. not configure and > engine/prim.i), you need to run BUILD-FROM-SCRATCH after checking out > a version. If you check in some generated files, you probably need > BUILD-FROM-SCRATCH, too. > > - anton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
