Message-Id: <200301180914.h0I9Eec13356@delorie.com> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Newsgroups: gmane.os.cygwin Subject: setup errors From: news@garydjones.mailshell.com User-Agent: Xnews/4.11.09 X-No-Archive: yes To: cygwin@cygwin.com X-Gate: Hamster/1.3.23.185 NewsToMail-Gate Date: Sat, 18 Jan 2003 10:05:55 +0100 I encountered a couple of problems updating my installation this morning. I use the download option, and then run setup again with the "Install from Local Directory" option to actually update Cygwin. Setup.exe version 2.249.2.5. While performing the latter stage, I got an error saying "Can't open (null) for reading: no such file" (I know, I've seen a number of messages in the archives about this, though not a clear explanation of what it really means). At that stage the main setup window showed that it was installing mutt-1.4-1, /usr/lib/mingw/txtmode.o (which I find a bit surprising because I had only selected the source to install). On completion of the install phase, I was told that "Installation incomplete. Check /setup.log.full for details" but that file does not exist: $ ls -la total 5 drwxr-xr-x 11 Gary users 0 Apr 6 2002 . drwxr-xr-x 11 Gary users 0 Apr 6 2002 .. -rw-r--r-- 1 Gary users 12 Apr 6 2002 .bash_history drwxr-xr-x 3 Gary users 0 Apr 6 2002 bin dr-xr-xr-x 11 0 0 0 Dec 31 1969 cygdrive -rwxr-xr-x 1 Gary users 135 Aug 20 17:10 cygwin.bat -rw-r--r-- 1 Gary users 766 Jan 18 07:12 cygwin.ico drwxr-xr-x 12 Gary users 0 Apr 6 2002 etc drwxr-xr-x 4 Gary users 0 Apr 6 2002 home drwxr-xr-x 20 Gary users 0 Apr 6 2002 lib lrwxrwxrwx 1 Gary users 123 Sep 15 18:18 library -> /usr/share/tc l8.0 -rwxr-xr-x 1 Gary users 84 May 26 2002 rxvt.bat drwxr-xr-x 2 Gary users 0 Apr 6 2002 sbin drwxr-xr-x 4 Gary users 0 Jul 20 19:35 tmp drwxr-xr-x 20 Gary users 0 Apr 6 2002 usr drwxr-xr-x 8 Gary users 0 Apr 6 2002 var (some spaces removed to avoid too much wrapping) instead: $ find / -name setup.log.full -print /var/log/setup.log.full Sadly I can't tell you what was in it, because a subsequent setup usage overwrote it (why does setup.log get appended to, and setup.log.full get overwritten?). So, 1) What does this can't open (null) really mean, please?, and 2) you can consider this a bug report about the message indicating the location of setup.log.full. -- 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/