X-Spam-Check-By: sourceware.org Date: Fri, 10 Feb 2006 14:32:51 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: make: rm: command not found Message-ID: <20060210193251.GD9482@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20060210174942 DOT GC6925 AT trixie DOT casa DOT cgf DOT cx> <009601c62e75$4717c7f0$a501a8c0 AT CAM DOT ARTIMI DOT COM> <20060210191612 DOT GA9482 AT trixie DOT casa DOT cgf DOT cx> <43ECE8BB DOT 7090306 AT equate DOT dyndns DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43ECE8BB.7090306@equate.dyndns.org> User-Agent: Mutt/1.5.11 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 On Fri, Feb 10, 2006 at 07:25:47PM +0000, Chris Taylor wrote: >Christopher Faylor wrote: >>On Fri, Feb 10, 2006 at 07:07:46PM -0000, Dave Korn wrote: >> >>>On 10 February 2006 17:50, Christopher Faylor wrote: >>> >>>>On Fri, Feb 10, 2006 at 09:45:44AM -0800, JefV wrote: >>>> >>>>>I re-installed cygwin and it seems to be working now. Strange. >>>> >>>>So, for those who keep track of such things, that's: >>>> >>>>One (1) reinstall to fix problems running "rm" under "make". >>> >>>Well, after all, it is only a /minor/ problem. >> >> >>Right. I'm just thinking that we can probably add a "problem solving" >>section to setup.exe which did the reinstallation automatically. >> >>Something along the lines of a "click here if you are having problems with >>a current installation" which would bring you to a screen that said: >> >> Type of problem: >> >> [.] "rm: command not found" under make >> [ ] cron can't access remote shares >> [ ] ssh not working (followed all instructions at pigtale.net) >> [ ] ssh not working (followed all instructions at >> networksimpcity.net) >> [ ] screen flashes when clicking on cygwin icon >> . >> . >> . >> >>Then setup.exe could know that, e.g., it takes one reinstall to fix the >>"rm" problem, four reinstalls to fix the pigtale.net ssh problem, and >>nine reinstalls to fix the networksimpcity.net ssh problem. >> >>This will take additional time, of course, but the eventual result would >>be problem-free cygwin installations. > >Actually, there could be a good idea in amongst that ;) > >Give setup the ability to run cygcheck, and have a problem-report >submission section built into it. >Give them email address and description fields, and it could send the >mail for them, thus eliminating the lack of a cygcheck (to an extent >anyway, not everyone would follow this, of course).. > >I know, I know, PTC... If I could, I would. The problem with that suggestion is that if cygcheck didn't run (typically a 2 reinstall problem) then you could get into some kind of weird loop. Add the requirement for checking how to send email to the mix and it might cause that OS wrapping problem that I reported earlier. This could really screw up a person's computer. cgf -- 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/