32-bit/64-bit sharing of Local Package Directories

Nellis, Kenneth Kenneth.Nellis@xerox.com
Mon Nov 17 19:52:00 GMT 2014


> From: Andrey Repin
> 
> I think you've used your current installation directory a little too long.
> :) Delete the setup.log{,.full}, they are no longer placed along the
> Cygwin setup executable. Mine's not been changed since september.

Hmm... Okay, I see that. Deleted! Thanx for that.
I also see like-named files in /var/log.

$ find /cygdrive/c/cygwin* -name 'setup.log*'
/cygdrive/c/cygwin/var/log/setup.log
/cygdrive/c/cygwin/var/log/setup.log.full
/cygdrive/c/cygwin64/var/log/setup.log
/cygdrive/c/cygwin64/var/log/setup.log.full
$

But I also notice that like-named files are also occasionally created
in my now-shared folder where my two setup-x86*.exe files reside:

$ ls -ld setup.log*
-rw-r--r-- 1 knellis Domain Users 374 Nov 17 13:04 setup.log
-rw-r--r-- 1 knellis Domain Users 374 Nov 17 13:04 setup.log.full
$ cat setup.log
2014/11/17 13:04:41 Starting cygwin install, version 2.852
2014/11/17 13:04:41 User has backup/restore rights
2014/11/17 13:04:41 Current Directory: C:\Users\knellis\Documents\Installers\Cygwin
2014/11/17 13:04:41 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access.
2014/11/17 13:04:46 Ending cygwin install
$

(setup.log.full is identical.)

But, experimenting, I've hidden these files and rerun Setup, and they don't
always get recreated, so I'm curious as to what's going on.

So, it seems there is still a name conflict between the 32-bit and
64-bit versions of these files as first reported.

--Ken Nellis

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list