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: Wed, 20 Dec 2000 19:19:07 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Cc: dkarr AT tcsi DOT com
Subject: Re: new install of cygwin with pdksh doesn't work
Message-ID: <20001220191907.F25109@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com, dkarr AT tcsi DOT com
References: <uyu27ybtv7 DOT fsf AT tcsi DOT com> <20001220183538 DOT A24933 AT redhat DOT com> <uyk88ubqlv DOT fsf AT tcsi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <uyk88ubqlv.fsf@tcsi.com>; from dkarr@tcsi.com on Wed, Dec 20, 2000 at 03:49:32PM -0800

On Wed, Dec 20, 2000 at 03:49:32PM -0800, David M. Karr wrote:
>>>>>> "Christopher" == Christopher Faylor <cgf AT redhat DOT com> writes:
>  Christopher> On Wed, Dec 20, 2000 at 02:39:08PM -0800, David M. Karr wrote:
>  >> I have a relatively recent install of cygwin, along with pdksh-2.14.
>  >> I have scripts that reference "/bin/ksh" that work fine.
>  >> 
>  >> Today I've been setting up these tools on another PC, and now when I
>  >> execute "ksh", I get the following:
>  >> 
>  >> ksh: /cygdrive/d/dmk/.bashrc[1]: syntax error: `in^M' unexpected
>  >> 
>  >> I'm sure this has something to do with line endings, but I don't
>  >> understand what has to be done.
>
>  Christopher> Remove the ^Ms in .bashrc.
>
>I have none.  These are the exact same files I used on the other PC
>that is working fine.  I copied them directly from the PC that doesn't
>have the problem to the PC that does have the problem, without change.

What are you using to verify this?  od -c should show you if your
supposition that there are no ^Ms in your file is correct.

I would not be surprised to find out that you are wrong and that your
.bashrc file has lines that end with ^M^J(\r\n).

Editing the file with 'vi -b' should also show any ^Ms.

If you really don't have any ^Ms in your file then I am at a loss as
to why they would show up in your error output.

cgf

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