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 name of the executable though, and I'm not sure what else is workable.
Cheers,
Derek
Conrad T. Pino wrote:
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 `all-am'. Making all in zlib make[2]: Nothing to be done for `all'. Making all in diff make[2]: Nothing to be done for `all'. Making all in src rm: cvs: is a directory make[2]: *** [cvs] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Titanium:~/projects/cvs-1.12.12 conradtpino$
The problem occurs because the MacOS file system appears to be case insensitive with respect to file names i.e. both of the following do the same thing:
ls CVS ls cvs
I'm seeing the error for the first time because I checked out with a revision tag instead of downloading a tar ball.
I can work around the problem by using "export" instead of "checkout" command.
The question becomes: Is it worthwhile fixing the build to deal with case insensitive UNIX file systems?
Conrad
_______________________________________________
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs
_______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
