Igor Pechtchanski wrote:
On Thu, 11 Nov 2004, bruno patin wrote:
Christopher Faylor wrote:
> Also, I believe that Gerrit suggested sending the contents of the setup
> log files.
>
> [snip]
>
> I appreciate that you're trying to think of solutions here but there
> have already been a couple of suggestions that no one seems to have
> bothered to follow through on. Why not just humor us and provide the
> debugging info that we're asking for?
........................ 3 the setup.log file (this mail) ......................................
Hope that helps BPatin
This setup.log doesn't show any install actions whatsoever. All it shows is that you've downloaded a bunch of packages.
I suspect this may have something to do with that "Cannot open setup.log for writing" error message. Try running "c:\cygwin\bin\chmod a+w setup.log setup.log.full" from a CMD prompt in "c:\cygwin\var\log" and then re-running setup. Also, setup.log.full should contain more detailed error messages after a failed setup run (beware -- that file is overwritten on every run of setup). Igor
Igor,
I've no setup.log created in /var/log in fact what I sent you was bullshit as it is only the result of my dowload as I see it (first time I'm really examining the internal of setup sorry, it works too well). Result is that there is no file in /var/log. Can be a real clue.
BPatin
