Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 16 Apr 2001 21:34:30 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: Cygwin <cygwin AT cygwin DOT com>
Subject: Re: RCS 5.7 Patches
Message-ID: <20010416213430.B23129@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: Cygwin <cygwin AT cygwin DOT com>
References: <3ADB6D30 DOT BF2C5172 AT lightbridge DOT com> <00b801c0c6d2$5445db70$c000000a AT costa1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <00b801c0c6d2$5445db70$c000000a@costa1>; from costa@cade.com.br on Mon, Apr 16, 2001 at 09:07:02PM -0300

On Mon, Apr 16, 2001 at 09:07:02PM -0300, Andre Oliveira da Costa wrote:
>I've had a couple of problems with RCS myself in the past, and with the
>handy assistance of many people from this list I finally managed to do it. I
>have recently had to recompile/reinstall RCS 5.7 on my NT4 w/ cygwin, and
>these were the steps I followed:
>
>* apply patch to RCS sources (refer to msg
>http://sources.redhat.com/ml/cygwin/2000-10/msg00545.html)
>* temporarily link /bin/sh to /bin/bash
>* run "./configure" on the main RCS src dir
>* run "make && make install" on the same dir
>* [optional] restore /bin/sh to its original executable (if you don't mind
>using the 460KB -- more feature rich -- bash executable instead of the 68KB
>sh executable, you don't have to restore the link)
>
>Be advised, though, that RCS will only work with recent cygwin1.dll
>snapshots because of an obscure problem with some inner functions (Corinna
>posted a message a while ago about this; it's on the archives). My system
>has been running snapshot 20010407 without a glitch for a couple of days
>already.

I hate it when this kind of advice gets into the archives.

The "Just link /bin/sh to /bin/bash" advice is IMO always wrong.

If /bin/sh is misbehaving it should be fixed.  Please don't just blindly
follow this advice.  Instead, participate in an open source and work
towards a solution rather than just narrowly focusing on getting your
immediate problem solved.

Of course, it would help if we understood exactly what was wrong with
/bin/sh that required this link...

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple