X-Spam-Check-By: sourceware.org
Message-ID: <31b7d2790610031024sf315d8ck3d35680f74b8bceb@mail.gmail.com>
Date: Tue, 3 Oct 2006 18:24:33 +0100
From: "DePriest, Jason R." <jrdepriest AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: updated bash to latest 3.1.17(8)-release; startup has errors now
In-Reply-To: <eftt2f$5rm$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <31b7d2790610021512m6093d076i6609b5fc21c55030 AT mail DOT gmail DOT com> 	 <45219876 DOT 40465402 AT dessent DOT net> 	 <20061002230357 DOT GD2949 AT trixie DOT casa DOT cgf DOT cx> 	 <4521A351 DOT 9090906 AT gmail DOT com> 	 <31b7d2790610022224o7db4dc45pea5f4a63cb62dde6 AT mail DOT gmail DOT com> 	 <eftt2f$5rm$1 AT sea DOT gmane DOT org>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 10/3/06, mwoehlke <> wrote:
> DePriest, Jason R. wrote:
> > This google search was pretty much worthless when I ran it before I
> > sent my message in:
> > bash "command not found" site:cygwin.com inurl:ml
>
> If you've STFLA'd, it is good to mention this when asking your question. :-)
>
> > vi did not show any unusual line endings (CR/LF) in /etc/profile
> > before I sent my message in
>
> ...and you know to look for '(dos)' in the status line, right? Although
> as Larry pointed out, this is only reliable if vi[m] is configured a
> certain way; ultimately, you might want to just try running d2u on it
> regardless of what you *think* the line endings are. (Also, have you
> checked that there is not some OTHER script being called at login, say
> ~/.bash_profile, ~/.bashrc, etc) that has 'bad' line endings?)
>
> > I noticed that the cygcheck output said things weren't there when a
> > manual check shows that they are there and that they are in the path
> > that cygcheck says it is checking.
> >
> > For my issue, not the thread hijacking 'make' issue, I do not have a
> > dual-core or hyperthreaded system.
>
> Hint: that was satire. ;-)
> (And to explain/ruin the inside joke, 'make 3-81' was the previous
> problem-that-everyone-reported-without-RTFRN'ing)
>
> > I did read the release notes when they came out.  The ANNOUNCE list is
> > the only one that I read all the messages for.  It did not look like
> > it should be causing the issues I am having.
>
> Ok, but again you should have mentioned that in your first e-mail...
> Otherwise, as you can see, people jump to the obvious conclusion.
>
> Plus, the more information you give off the bat, the more likely someone
> is to notice a problem and come up with a solution.
>
> --
> Matthew
> "I don't question your existence -- God" (seen on a church billboard)
>
>
> --

For some reason, I forgot to look for the [dos] as I thought vi would
just show me the ^M at the end all the time.

I am a bonehead for that.

both od -c and vi -b show that, sure enough, there are plenty of \r\n in there.

Oops and sorry to bother everyone, but at least I learned something out of it.

-Jason

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/