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:date:from:to:subject:in-reply-to:message-id
	:references:mime-version:content-type; q=dns; s=default; b=Cwtlt
	2fPx+DQ+QNmcyYRozFpPr30O8Zi2rpw3DjR0UVqcHnXP4DeIbOyXpcw2Sl9+Pg4R
	w/OGZhx0XnasWJU3NvSq81EMO9Vixm3/4vZf8ze6w0EwXChNWvyTv9Gf/rbViOJk
	cyziChj7+Mj/eCkAQxrE2zVFpQ7rt5p1uJYSP0=
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:date:from:to:subject:in-reply-to:message-id
	:references:mime-version:content-type; s=default; bh=gmkefY0uzse
	/lG7dR3B+wqvGCBg=; b=WFR5ZvkjbOCK6PukIBCGAwrbjd1qBbbAC9i9VcCXP9H
	eyIwLtHNPKdQcJieBW88mCX2Z+KqwzaznVr60FBRq39pUiM7RJe4MSPvszIyl8Em
	0Y+58ko1B8CqgQEsszmtL1ELhvRSD52uZfXiMGQ40ef+oyY9rPDev6rO8H/WFn9Q
	=
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.9 required=5.0 tests=AWL,BAYES_50,SPF_HELO_PASS,SPF_PASS,TVD_RCVD_IP autolearn=ham version=3.3.2
X-HELO: ripple.fruitbat.org
Date: Tue, 15 Apr 2014 14:51:04 -0700 (PDT)
From: "Peter A. Castro" <doctor AT fruitbat DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
In-Reply-To: <53435811.6080104@cygwin.com>
Message-ID: <alpine.LNX.2.00.1404151442580.9344@ming.fruitbat.org>
References: <20140404083359 DOT GD2508 AT calimero DOT vinschen DOT de> <loom DOT 20140404T113717-470 AT post DOT gmane DOT org> <20140404113738 DOT GF2508 AT calimero DOT vinschen DOT de> <loom DOT 20140407T124141-753 AT post DOT gmane DOT org> <20140407112313 DOT GA17922 AT calimero DOT vinschen DOT de> <5342D299 DOT 1040101 AT cygwin DOT com> <loom DOT 20140407T225832-327 AT post DOT gmane DOT org> <534322E8 DOT 8070701 AT cygwin DOT com> <alpine DOT LNX DOT 2 DOT 00 DOT 1404071509070 DOT 9344 AT ming DOT fruitbat DOT org> <534350BD DOT 9040806 AT cygwin DOT com> <20140408015026 DOT GA2359 AT ednor DOT casa DOT cgf DOT cx> <53435811 DOT 6080104 AT cygwin DOT com>
User-Agent: Alpine 2.00 (LNX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-IsSubscribed: yes

On Mon, 7 Apr 2014, Larry Hall (Cygwin) wrote:

> On 4/7/2014 9:50 PM, Christopher Faylor wrote:
>> On Mon, Apr 07, 2014 at 09:28:29PM -0400, Larry Hall (Cygwin) wrote:
>
> <snip>
>
>>>> 2) Packaging changes of setup.exe have made extracting the version string
>>>>      impossible, save for actually running setup, which isn't something 
>>>> I'm
>>>>      going to do on a daily basis.  If there is a method of extracting 
>>>> this
>>>>      info from it, please do tell me how.
>>> 
>>> I'm assuming it used to just be in the RC file in the past.  Didn't look
>>> in the history to trace it back.  But now it is generated and put in
>>> setup_version.c as a global constant setup_version.
>> 
>> setup.exe is packed with upx.  If you want to see the version string I
>> suppose you could unpack it with upx.
>
> Of course!  Why didn't I think of that?
>
> strings setup*.exe | grep setup-version
>
> This returns the version for a _decompressed_ setup executable.

This is, in fact, what I was doing before there was a change in the packer 
utility that I was unable to, at the time. build for myself.

I've just built a newer version of upx (and ucl, etc) and now I will start 
archiving setup, x86 & x86_64, (again).  Need to update my webpage 
automation to generate an access list, but atleast I'm grabbing and 
archiving them (again).

Thanks for bringing this (back) to my attention (again).

In general, though, unless and until there is a significant change to 
the setup.ini format, the most recent installer *should* just work.

-- 
--=> Peter A. Castro
Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com
 	"Cats are just autistic Dogs" -- Dr. Tony Attwood

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