X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<4D54A4B3.5070504@verizon.net>
References:	<4D548DE2 DOT 6010300 AT verizon DOT net> <4D54982F DOT 3080700 AT verizon DOT net> <4D54A4B3 DOT 5070504 AT verizon DOT net>
Date:	Thu, 10 Feb 2011 20:13:06 -0800
Message-ID:	<AANLkTimAqX1A4TB7TbshZC0nedhEkdHf-k3B1CbXXzSG@mail.gmail.com>
Subject:	Re: 1.7.7: Windows 2003 R2 WOW64: Cygwin installation fails
From:	Kenneth Wolcott <kennethwolcott AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Thu, Feb 10, 2011 at 18:53, Gerry Reno <greno AT verizon DOT net> wrote:
> On 02/10/2011 09:00 PM, Gerry Reno wrote:
>> On 02/10/2011 08:16 PM, Gerry Reno wrote:
>>
>>> After having so much difficulty post-upgrade Cygwin 1.5 to 1.7 on my
>>> Windows 2003 R2 WOW64 machine:
>>>
>>> =A0 =A0 I prepared a fresh installation of Windows 2003 R2 WOW64 and
>>> installed Cygwin 1.7.7 using setup.exe from the cygwin.com site.
>>>
>>> =A0 =A0 Conclusion: A fresh install of Cygwin 1.7.7 FAILS on Windows 20=
03 R2
>>> WOW64.
>>>
>>>
>>> There are numerous postinstall failures:
>>>
>>> =A0 =A0 Package: base-cygwin
>>> =A0 =A0 =A0 =A0 =A0 =A0 000-cygwin-post-install.sh exit code 128
>>> =A0 =A0 Package: coreutils
>>> =A0 =A0 =A0 =A0 =A0 =A0 coreutils.sh exit code 1
>>> =A0 =A0 Package: terminfo
>>> =A0 =A0 =A0 =A0 =A0 =A0 terminfo.sh exit code 35584
>>> =A0 =A0 Package: bash
>>> =A0 =A0 =A0 =A0 =A0 =A0 bash.sh exit code 128
>>> =A0 =A0 Package: terminfo0
>>> =A0 =A0 =A0 =A0 =A0 =A0 terminfo0.sh exit code 128
>>> =A0 =A0 Package: base-files
>>> =A0 =A0 =A0 =A0 =A0 =A0 base-files-profile.sh exit code 128
>>> =A0 =A0 =A0 =A0 =A0 =A0 base-files-mketc.sh exit code 128
>>> =A0 =A0 Package: man
>>> =A0 =A0 =A0 =A0 =A0 =A0 man.sh exit code 128
>>>
>>>
>>>
>>> The bash login shell fails:
>>>
>>> =A0 =A0 bash-4.1# echo $PATH
>>> =A0 =A0 /cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WI=
NDOWS/System32/Wb
>>> =A0 =A0 em:/cygdrive/c/Program Files (x86)/Microsoft SQL Server/90/Tool=
s/binn/
>>> =A0 =A0 bash-4.1#
>>>
>>>
>>> No PATH is set.
>>>
>>> =A0 =A0 bash-4.1# /usr/bin/cat /etc/profile
>>> =A0 =A0 /usr/bin/cat: /etc/profile: No such file or directory
>>>
>>>
>>> No system-wide profile.
>>>
>>>
>>> I've attached a cygcheck.out.
>>>
>>> Please let me know if you would like anymore information. =A0I'll keep
>>> this machine around as is for a few days if it will help.
>>>
>>>
>>> Regards,
>>> Gerry
>>>
>>>
>>>
>> I went and cleared out everything and started over but first moving the
>> DEP setting from All to Windows-only.
>>
>> This time the Cygwin installation completed without postinstall errors
>> and the bash login shell is working.
>>
>> =A0 =A0 What I think would be good is for Cygwin setup to detect and warn
>> =A0 =A0 about the DEP setting on Windows 2003 / Windows 2008.
>>
>>
>> What happened in my case was that I originally had a good installation
>> of Cygwin 1.5 on Windows 2003 that apparently worked fine with DEP in
>> the restrictive setting. =A0It was only after I upgraded it to Cygwin 1.7
>> that problems appeared.
>>
>> I'm now going to try a Cygwin reinstall on my original machine after
>> changing the DEP setting to see if the 1.7 upgrade installation can be
>> fixed.
>>
>>
>>
>
> I changed the DEP setting but in trying to reinstall the original
> upgraded installation, it gets into a vicious loop of:
>
> =A0 =A0Package file libgcc1 has a corrupt local copy, please remove and r=
etry.
> =A0 =A0 =A0 =A0And
> =A0 =A0Package file libssp0 has a corrupt local copy, please remove and r=
etry.
> =A0 =A0 =A0 =A0And
> =A0 =A0Package file libstc++6 has a corrupt local copy, please remove and
> =A0 =A0retry.
>
>
> I seem to be able to fix one at a time but not all. =A0Still trying.
>
> ...
>
> Ok, I finally got it all to reinstall but the installation is still
> broken. =A0Same problems. =A0Failed postinstalls, "Bad address" errors and
> no bash login shell.
>
> Anyone have any thoughts as to how to fix this installation? =A0The
> fallback of course is to wipe Cygwin off and do a complete new
> installation but I'm trying to avoid that if possible with all the
> configs I've made.
>
>
> Regards,
> Gerry

  Wipe Windoze off the disk and use Linux or *BSD or even Solaris :-)

  That would definitely solve the problem :-)

  No, I don't have an answer to help, but I thought I would try add some le=
vity.

Good luck,
Ken Wolcott

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

- Raw text -