X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:content-type:content-transfer-encoding; q=dns; s=
	default; b=PGE+nRQT0XI9SjiKSogI+6Cc6QMtHcZKoqpy1O69uXqBy3iyOeqqi
	Y1qcCdiBOSynemjy6Eralh6EtuUJwMggj75YuEW/2OQ5zJ9k24pOQ7QydhhXS/tk
	N4hjY/T9TRmlmUGyIL+Io6molPLyfvqmsHuUzAo2H6J4MdV2eKFiNk=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:content-type:content-transfer-encoding; s=default; bh=A
	jcVT1cH4Qv4FChR5T+v9FFvhHE=; b=YNtgcB53YVjFVx4xVF4OUL3PRvgyqbKQz
	4dIHubLU6BcfIlyiAxkNxJR/3aR71so059GF9v7LggN+2UdEzbiQ0ilUW5NqJ/CF
	Krssn53EnKexWbuShJJzrJMp3oyoADmegvQhJryB3xTUwLWslS1KSh34P0thH2ig
	xOvORHPDPQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.6 required=5.0 tests=BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	p3plsmtpa07-08.prod.phx3.secureserver.net
Message-ID:	<528C23B6.20701@w5pny.com>
Date:	Tue, 19 Nov 2013 19:51:34 -0700
From:	Harry G McGavran Jr <w5pny AT w5pny DOT com>
Reply-To:	w5pny AT w5pny DOT com
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem with latest setup-x86.exe

Corinna Vinschen writes:
> > Achim Gratz writes:
> > > Corinna Vinschen writes:
> > >> I just explained that in a reply an the cygwin-apps list:
> > >> http://cygwin.com/ml/cygwin-apps/2013-11/msg00075.html
> > >>
> > >> I applied a patch to setup which should fix the issue.
> > >
> > > The patch WJFFM.
> > >
> >
> > But in line 266 of main.cc set_cout() is still called
> > if unattended_mode -q (or --help) is set.
>
> Sure.  The problem was not the set_cout function but overloading the
> fopen function.

FWIW -- what brought me to line 266 was that I started playing
with the latest setup-x86.exe (The 17-Nov. 2013 one) in a cmd
window and noticed that the problem only existed with -q or --help.
I normally use setup.exe with -q so I was seeing this all the time.
So after looking at main.cc it was too hard to pass up line 266
as a possible culprit.

A bit more interesting though is that later I started using the
Windows debugger under the cmd window on that same setup-x86.exe
and could see the null pointer problem, but of course there were
not symbols or source.  So, for grins I decided to decompress
it with "upx -d" and voila, it fixed the problem as long as I ran
the uncompressed version.  For further grins, I decided to
try compressing it again and most of the common options brought
the problem back -- BUT -- if I used "--compress-exports=0"
in upx, then I got a compressed version that doesn't have the
problem.  Even with --best and --compress-exports=0 I get
a version that works.

So, this is just FWIW -- other executables compress with upx and
work just fine. Previous versions of setup (prior to the incantations
of the current version) work just fine -- so not being a windows
person any more that I absolutely have to, I'm not going to pursue
this any further, but this might be useful information for someone someday.

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