X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: Cygwin broken after update (PATH problem?) Date: Mon, 23 Oct 2006 14:39:27 +0200 Message-ID: In-Reply-To: <07a501c6f67d$252f9ca0$a501a8c0@CAM.ARTIMI.COM> From: "Com MN PG P E B Consultant 3" To: "Dave Korn" , Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k9NCdpfa023458 > >> Your /etc/profile has DOS-style CRLF line endings. > > > > Well, the problem is that there *is* no /etc/profile at all. > > Well, that tells us two things: > > 1) Setup must have failed part-way through. Normally > re-running it, with > "Install from local package directory", and clicking through > all the default > options, and letting it run to completion should fix any > problems, but I see > you tried that already. Hmm. No, I run setup again from the *website*. But I think this must be even more safer than just doing it locally. > >> You will, I'm sure, not have updated your version of > bash without reading > >> the relevant release announcement, > > > > What type of announcement? > > The release announcements, that are posted to the > cygwin-announce list as > well as to the main cygwin list, every time that a cygwin > package is updated. > Weren't you curious about what updates you were going to get > and in what way > they would be different from what you already had installed? Honestly, no, not at all. Yes, this makes me an ignorant, but the main reason I went to redo the setup, was that I wanted to install a new package, and when doing this I thought it might be a good idea to update everything, to get the most recent bug fixes and so on. So I wasn't that interested in new features. > This one: > > http://cygwin.com/ml/cygwin-announce/2006-09/msg00006.html > > seems to explain at least part of your problem: self-overwriting error > messages are a sign of CRLF line-ends. I see. Indeed I did modify the profile, and although I normally take care about the line endings (the editor is set to keep line endings style), it might be that I also had used on one occasion a different editor which did not observe this policy. Not very likely, but I don't want to rule out this possibility. But this would not explain why the /etc/profile got *erased*. However, the announcement says that one should not have bash running while doing the setup. I think I did have a cygwin window open, running zsh on top of bash. > > I went to http://cygwin.com/ (on this > > page, there is definitely no "release announcement" to see), > > Not all the documentation at the cygwin.com website is on > the front page. > It wouldn't all fit. You're expected to have browsed the > docs, faq and > mailing-list summaries of your own accord. (The fact that you're here > suggests you /did/ read the mailing-list summary page...) Yes, I misunderstood you here. I thought you wanted to suggest that the announcements of the most recent release were supposed to be always published on the front page (or at least represented via a direct link, as it is the case on some other software homepages). > > So it seems that setup did > not overwrite, > > but delete it, which is really kind of strange. > > Yep, it's absolutely not meant to do that. Which means > that something went > badly wrong, but it's a bit hard to guess what. > > If setup.exe doesn't repair the system for you, you can get > a fresh copy of > /etc/profile out of /etc/defaults/etc. Thank you, I will try it. Ronald -- Ronald Fischer (phone +49-89-63676431) mailto:mn-pg-p-e-b-consultant-3 DOT com AT siemens DOT com -- 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/