-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad T. Pino <[EMAIL PROTECTED]> writes:
> I'm seeing the same build problem on both stable & feature:
>
> Titanium:~/projects/cvs-1.12.12 conradtpino$ make
> make all-recursive
> Making all in lib
> make all-am
> make[3]: Nothing to be done for
Conrad T. Pino wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
From: Derek Price [mailto:[EMAIL PROTECTED]
I never thought it was worth coming up with a more automated solution,
but you're welcome to try. I would argue against changing the name of
the executable though, and I'm
Incidentally, I thought this was documented somewhere other than the
email list, but I don't see it. I've added a note to INSTALL on stable
and INSTALL-CVSon feature.
Cheers,
Derek
Derek Price wrote:
This is a well-known problem. The workaround is to use a build
directory. i.e.:
cvs co c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
> From: Derek Price [mailto:[EMAIL PROTECTED]
>
> I never thought it was worth coming up with a more automated solution,
> but you're welcome to try. I would argue against changing the name of
> the executable though, and I'm not sure
This is a well-known problem. The workaround is to use a build
directory. i.e.:
cvs co ccvs
cd ccvs
mkdir build
cd build
../configure
make
I never thought it was worth coming up with a more automated solution,
but you're welcome to try. I would argue against changing the nam