-----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 `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?
The typicaly way that I build on case-insensitive filesystems is like
this:
cvs checkout ccvs
cd ccvs
mkdir objdir
cd objdir
../configure && make && make check
this means that all of the derrived files are in the ccvs/objdir
subdirectory. If I am going to build for multiple architectures
out of the same set of sources, I have been known to use the
following directory names:
obj.macosx2 # MacOS 10.2
obj.macosx3 # MacOS 10.3
obj.solsparc9 # Solaris 9 on Sparc hardware
obj.solsparc8 # Solaris 8 on Sparc hardware
obj.solsparc7 # Solaris 7 on Sparc hardware
obj.aix43 # AIX 4.3
obj.fbsd42 # FreeBSD 4.2-RELEASE
obj.fbsd410 # FreeBSD 4.10-RELEASE
obj.nbsd16 # NetBSD 1.6
obj.nbsd299 # NetBSD 2.99.15
obj.rh73 # Redhat 7.3 i386 GNU/Linux
obj.fc3 # Fedora Core 3 i386 GNU/Linux
obj.unicos # Unicos 9.0 Cray Y-MP EL
instead of 'objdir' as the place where I build and test out of one
checkout of the sources...
Your experience may be different.
I almost never actually build directly in the 'ccvs' directory as it was
checked out (I try it once per release as we are getting close to make
sure it still works).
Enjoy!
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCeGT03x41pRYZE/gRAvOQAKDKvElDg9X4RFPYGc5vtK2q1F0xGwCgxBov
+hBA43zL1skrlMklP/GJtf0=
=U12V
-----END PGP SIGNATURE-----
_______________________________________________
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs
