Repeated setup msgs: "Can't open (null) for reading: No such file"

Repeated setup msgs: "Can't open (null) for reading: No such file"

[fergus]

Yow, 2 hours and 300+ MB later. "Download and Install from the Internet"
rather than "Install from Local Directory" as in my recent post. I proceeded
exactly as before, selecting absolutely everything for installation and
checking the SRC tickbox too. Almost no errors: Cygwin itself works
properly, as before, but this time the source files were correctly located
in the appropriately named directory under /usr/src/ (NOT a trivial subset
of them in /usr/src/src/). Two strangenesses:

(i) at the appropriate time I got an error message box containing the text:

Warning: deleting "c:\Cygwin/usr/src/expect-20010117-1/tcl" so I can make a
directory there

(ii) at the very end, message box was presented saying "Installation
incomplete. Check /setup.log.full for details.

Apart from the minor glitch at (i) I was not aware of any installation
problems and maybe that was the only one, but I do not know what to look for
in the 7 MB 102,000 line file that is setup.log.full.

Summarising: I think setup.exe still contains minor buglets relating
entirely to the location of source files under /usr/src/. A full
installation from a Local Directory or from the Net seems to result in a
fully functional Cygwin. BUT the Local installation leads to almost total
failure locating source files under /usr/src/. The Net installation is, or
seems to be, almost completely successful apart from a small problem with
the creation of /usr/src/expect.... and with the final "Installation
incomplete" message which might refer to one visible, or to very many
invisible, errors.

I have all 4 of setup.log.* files (two each for Local and Net installation)
but they are extremely large.

Fergus


--
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/

RE: Repeated setup msgs: "Can't open (null) for reading: No such file"

[Robert Collins]

> -----Original Message-----
> From: fergus@bonhard.uklinux.net [mailto:fergus@bonhard.uklinux.net] 
> Sent: Thursday, May 09, 2002 9:29 PM

> I have all 4 of setup.log.* files (two each for Local and Net 
> installation) but they are extremely large.

Please send these to me, it sounds like I should be able to make use of
them.

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/

RE: Repeated setup msgs: "Can't open (null) for reading: No such file"

[Robert Collins]

> -----Original Message-----
> From: fergus@bonhard.uklinux.net [mailto:fergus@bonhard.uklinux.net] 
> Sent: Thursday, May 09, 2002 7:13 PM

> This phenomenon got some traffic during 4th/5th May, but 
> discussion seems to have died?

The work week...
 
> For 00th time did a fresh install today. Latest setup.exe.

Please define latest. A version number will do. (I can think of three
definitions off-hand)>
 
> This is from Local Directory, by the way: but all .tar.bz2 
> and -src.tar.bz2 and .tar.gz and -src.tar.gz are present in 
> the approprate directory under /release/, for [prev] and 
> [test] as well as [curr].

Ok.
 
> Select absolutely everything. This time I selected all the 
> .src files as well, which I've never botherd with in the 
> past. During installation (which btw has been successful : 
> everything I've tried, works, as it always has in the past) 
> repeated message boxes
> 
> "Can't open (null) for reading: No such file"

Urgh. I really want to squash that bug.
 
> were presented to screen, always with reference to filename 
> -src. Just kept on clicking the message boxes away until 
> eventually the installation groaned its way to completion.
> 
> I observe :
> 
> 1. Three sets of source files _have_ actually been installed. 
> They are in
> 
>     /usr/src/src/diff
>     /usr/src/src/gperf
>     /usr/src/src/m4
> 
> 2. Note double /src/. Is this the correct location?

No. That is definitely faulty.
 
> 3. For each of these applications, there is no versioning in 
> the filename (as in bash-2.05a-3 for instance) : they are 
> just called diff, gperf and m4. Coincidence or what?

That is up to the packager.
 
> So it looks as though the "Can't open ..." failure is almost 
> but not quite reducible to a file-naming glitch? Dunno, but 
> hope this helps.

It may. Thank you for the detailed analysis. This is really good stuff.
 
> I have not tried a network installation from scratch, also 
> incorporating -src files. But I will, now.
> 
> They are huge and awful (2 MB), so I will only send the 
> matching setup.log and setup.log.full if requested.

Please send privately to me (bzip2'd).

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/

Repeated setup msgs: "Can't open (null) for reading: No such file"

[fergus]

This phenomenon got some traffic during 4th/5th May, but discussion seems to
have died?

For 00th time did a fresh install today. Latest setup.exe.

This is from Local Directory, by the way: but all .tar.bz2 and -src.tar.bz2
and .tar.gz and -src.tar.gz are present in the approprate directory under
/release/, for [prev] and [test] as well as [curr].

Select absolutely everything. This time I selected all the .src files as
well, which I've never botherd with in the past. During installation (which
btw has been successful : everything I've tried, works, as it always has in
the past) repeated message boxes

"Can't open (null) for reading: No such file"

were presented to screen, always with reference to filename -src. Just kept
on clicking the message boxes away until eventually the installation groaned
its way to completion.

I observe :

1. Three sets of source files _have_ actually been installed. They are in

    /usr/src/src/diff
    /usr/src/src/gperf
    /usr/src/src/m4

2. Note double /src/. Is this the correct location?

3. For each of these applications, there is no versioning in the filename
(as in bash-2.05a-3 for instance) : they are just called diff, gperf and m4.
Coincidence or what?

4. On the other hand, byacc-src.tar.gz was not successfully installed into
/usr/src/src/byacc/, so this lack of numbering can't be quite the reason for
this strange phenomenon

5. All the 3 successfully installed sets of -src files arrive compressed
in -src.tar.gz format not -src.tar.bz2 (but there are lots of others like
this)

So it looks as though the "Can't open ..." failure is almost but not quite
reducible to a file-naming glitch? Dunno, but hope this helps.

I have not tried a network installation from scratch, also
incorporating -src files. But I will, now.

They are huge and awful (2 MB), so I will only send the matching setup.log
and setup.log.full if requested.

Fergus


--
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/