Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Robert Collins" To: "'Alan Hourihane'" , Subject: RE: setup.exe problems Date: Wed, 12 Jun 2002 06:35:59 +1000 Message-ID: <000301c21187$9867ecc0$0200a8c0@lifelesswks> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <20020611185208.GN1102@fairlite.demon.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > -----Original Message----- > From: cygwin-owner AT cygwin DOT com > [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Alan Hourihane > Sent: Wednesday, 12 June 2002 4:52 AM > To: cygwin AT cygwin DOT com > Subject: setup.exe problems > > > I always use the 'install from download directory' option when using > cygwin. > > I've just setup a fresh machine and installed with the > default installation. > > This missed out 'vi' for me. So I had to back in and manually > select it. > > But, when I go ahead to really install it I get... > > Can't open (null) for reading: No such file or directory > > This stopped 'vi' installing. > > This also happened once or twice during the default installation, but > I just hit OK and it continued. > > Oh, one point, I'm installing from a samba networked drive to my > local drive c: > > Any ideas ? This is a fairly right description. If we can pin this down, I hope to finally remove this bug. The usual cause is installing a package that is -not- in your local install dir. Can you do a ls -lR of your 'download directory', and send that + your two setup log files (.log and .log.full) to me bz2'd in private mail. Thanks, Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/