fsg@holos0.UUCP (Frank Glass) (01/19/89)
I have seen numerous posting in this and other newsgroups regarding problems getting RCS to run, but no solutions. I recently acquired RCS sources from one of the archive sites, and compiled it successfuly, but it still seems to have a problem with the diff on this machine. As there are many versions of diff out there in archive sites, I assume that one of them must solve my problem. I would appreciate help from anyone who could point me to the correct solution. Thanks in advance. -- Frank Glass Holos Software, Inc. Voice: (404) 496-1358 UUCP: ...!gatech!holos0!fsg
terry@eecea.eece.ksu.edu (Terry Hull) (01/21/89)
The solution to using RCS with XENIX is getting GNU diff. It works,
but there are a couple of things you shuold be aware of. First, it
uses lots of memory. It does it's work in core instead of on the
disk. Secondly, to compile GNU diff, you need alloca. I used the one
from GNU EMACS, and it seems to work fine.
As always, your mileage may vary. . .
--
Terry Hull Department of Electrical and Computer Engineering
Kansas State University
INTERNET: terry@eecea.eece.ksu.edu Manhattan, KS 66502
UUCP: rutgers!ksuvax1!eecea!terryjames@bigtex.cactus.org (James Van Artsdalen) (01/21/89)
In <1742@holos0.UUCP>, fsg@holos0.UUCP (Frank Glass) wrote: > [...] I recently acquired RCS sources from one of the archive sites, > and compiled it successfuly, but it still seems to have a problem with > the diff on this machine. Get GNU diff (latest release was 10/26 I think). It supports the options that RCS wants and works just fine. Also does those nifty context diffs, and runs substantially quicker than the AT&T diff (this may be because I compiled GNU diff with GNU C instead of PCC). I recall having some trouble getting GNU diff3 and rcsmerge to work together, but this isn't a serious problem and can probably be solved with a little effort. Warning: when installing RCS, be certain to *test* it before entrusting your sources to it. Check in a file, modify it, check in the new version, and make sure you can still get the original. If your diff fails, you might not get any errors until you tried to retrieve the original file... -- James R. Van Artsdalen james@bigtex.cactus.org "Live Free or Die" DCC Corporation 9505 Arboretum Blvd Austin TX 78759 512-338-8789
james@bigtex.cactus.org (James Van Artsdalen) (01/22/89)
In <538@eecea.eece.ksu.edu>, terry@eecea.UUCP (Terry Hull) wrote: > [...] Secondly, to compile GNU diff, you need alloca. I used the > one from GNU EMACS, and it seems to work fine. Ack! You should avoid the "portable" alloca() from GNU emacs at all costs, as it is hideously slow and can consume *large* amounts of memory. Truly it is a last resort. Surely Microsoft has alloca() in one of the libraries. AT&T keeps one in libPW, and GNU C has it built in if you declare #define alloca(n) __builtin_alloca(n) -- James R. Van Artsdalen james@bigtex.cactus.org "Live Free or Die" DCC Corporation 9505 Arboretum Blvd Austin TX 78759 512-338-8789