Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Upgrade the CVS command line tools UNIX
Type cvs -v in the terminal to see which version you have. More than likely you'll see Concurrent Versions System (CVS) 1.10 `Halibut' (client/server)

Here's how to compile version 1.11.1p1. These instructions will replace the existing Apple-supplied CVS files including the html documentation. By default, 'make' wants to install texi info files for the docs, but we're going to trash those and create html versions instead, as with Apple's distribution. Also we change the other default UNIX installation directories to use Mac OS X specific ones.

Read the rest of the article for the step-by-step instructions.

First, a couple of useful links:

CVS Release notes
CVS Download page

Download the 1.11 tar.gz file from the above download page, expand the archive, and then open a Terminal in the expanded folder and execute the following commands:
% setenv LDFLAGS '-framework Kerberos';
% setenv CFLAGS '-O3 -I/usr/include/gssapi/';
% ./configure

% make -j10

% sudo make install

% texi2html -split_node ./doc/cvsclient.texi;
% texi2html -split_node ./doc/cvs.texinfo;
% mv ./doc/*.html /Developer/Documentation/Commands/cvs/
[Editor's note: The options after the ./configure command need to be placed on the same line as ./configure, with a space between each argument. They are shown split here to improve readability. I have not personally tried this hint, so I can't vouch for its effectiveness.]
  • Currently 0.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (0 votes cast)

Upgrade the CVS command line tools | 4 comments | Create New Account
Click here to return to the 'Upgrade the CVS command line tools' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
make -j10 failed
Authored by: jean-pierre on Jan 03, '02 12:17:07PM
after following the instructions to the t, make failed for me. it finished making all for zlib and was chugging away at client.c and resulted in the following error text.
//lots clipped client.c:4199: undefined type, found `gss_buffer_desc' client.c:4200: undefined type, found `OM_uint32' client.c:4201: undefined type, found `gss_name_t' client.c:4228: undefined type, found `OM_uint32' client.c:4229: undefined type, found `OM_uint32' cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode make[3]: *** [client.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2
if you read the update log you will see that 1.11 doesn't bring a whole lot of changes for standard cvs users aside from the repair of an occasional false positive from the packaged diff.

[ Reply to This | # ]
Configuration parameters
Authored by: Velociped on Jan 03, '02 12:31:29PM
"The options after the ./configure command need to be placed on the same line as ./configure, with a space between each argument."

While the aforementioned is true, there is another option...

Using a <space> "\" (backslash) at the end of each line will allow one to distribute the parameters across several lines - as displayed in the hint.


% ./configure \
--prefix=/usr \
--localstatedir=/private/var \
--sysconfdir=/private/etc \
--mandir=/usr/share/man \
--infodir=~/.Trash \
--with-gssapi=/usr \


[ Reply to This | # ]
cvs install good under csh shell
Authored by: outofcontrol on Jan 03, '02 10:32:10PM
I just installed the latest cvs-1.11 as per the instructions and had no problem. No problem that is after I set the correct shell. If I am not mistaken OS X uses tcsh as the default shell, and these cvs install instructions are for csh. So simply type 'csh' before following the commands and then return to your shell with tcsh or bash if you use that shell as I do. Here are the instructions that can be cut and pasted into your shell to install cvs-1.11 for you. Be sure you have downloaded the tarball and uncompressed it first, then cd into the cvs-1.11 directory root before you cut and paste these instructions.
setenv LDFLAGS '-framework Kerberos';
setenv CFLAGS '-O3 -I/usr/include/gssapi/';
./configure \
--prefix=/usr \
--localstatedir=/private/var \
--sysconfdir=/private/etc \
--mandir=/usr/share/man \
--infodir=~/.Trash \
--with-gssapi=/usr \
make -j10
sudo make install
texi2html -split_node ./doc/cvsclient.texi;
texi2html -split_node ./doc/cvs.texinfo;
mv ./doc/*.html /Developer
Note: I have put bash as the last line in the code, you will want to put whatever your current shell is instead.

Hope this helps.

[ Reply to This | # ]
cvs install good under csh shell
Authored by: Velociped on Jan 04, '02 10:10:36AM


Two quick comments...

I am not sure what caused your unsuccessful compile the first time through, but your default/login shell should make no difference. Not only that, but the shell called by the "configure" script is the Bourne shell — not csh.

#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated automatically using autoconf version 2.13
# Copyright (C) 1992, 93, 94, 95, 96 Free Software Foundation, Inc.
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.

[ ... ]

Next, if you do summon csh within which to run the compile and make routines, the technique given for exiting at completion is not correct. Instead, simply issue an exit command following the execution. In effect, what has been done by following the instructions provided above is to spawn a bash shell — within a c shell — within a bash shell (assuming the latter to be the login/default shell).

As an example, witness the following little experiment...

computer (/Users/himay) $echo $SHELL
computer (/Users/#me#) $csh
[computer:~] #me#% tcsh
[computer:~] #me#% sh
computer% exit
[computer:~] #me#% exit
[computer:~] #me#% exit
computer (/Users/#me#) $echo $SHELL

More important to a successful compile of this (or any other system wide, service type software) is to be root# or issue the commands through sudo


[ Reply to This | # ]