Re: busted 'make swig-py'...

Matt Kraai <kraai@alumni.cmu.edu> writes:

> > And here's what I discovered: if I now run 'gmake swig-py', everything
> > works. And then *afterwards*, plain old 'make swig-py' works for me!
> >
> > Anyone have any ideas? Wanna see my generated build files?
>
> Since it's dropping the last part of the command, could you be
> running into a maximum line length restriction?

I told Ben that I think his scenario has the following two truths:

(1) 'make swig-py' simply isn't generating .c from .i; 'gmake swig-py' is.

(2) the reason his 'make swig-py' works after a successful 'gmake
    swig-py' is because the gmake already did the .i -> .c part, so
    make skips that step. This is all part of the regular dependency
    checking that is, after all, the whole point of Makefile systems. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 28 17:46:30 2003