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:mime-version:message-id:from:to:subject
	:content-type:date; q=dns; s=default; b=MDGunz8+nw5NwXrK4uwJ0FLe
	gAeq2a6pbUkvK+0wRcBwB4clZbucDh322sAnGN+UdQV2ZL6xLxu8sEQ5qPFRsesi
	+LTaspdsc/PwsnNRGAesWNtDGufcMf4YYRuSXLMjqxj3gUYpJjwVRX5tO0/Kplbf
	7wF/xJdGkXN2EFTaIDc=
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:mime-version:message-id:from:to:subject
	:content-type:date; s=default; bh=a0wpcXWpbtQ773JwgnBr4BLUwuA=; b=
	nGprzD9MY84AE6ZddQEa6HorAZdbU/f4FZPTNGBl5OPYgeOatF8MaZDHDGEdi+S1
	5LJWZqPSNzWw4VqIsNOWShvr/luXElY4UxErckvBQlG2bJKO0w4DQVHGBY6hOeyx
	qosCGbWBJ66kNU+yyawH2ODhYwGnUhWCiZLTtKgdLP4=
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=-0.3 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*M:app, H*MI:app, Hx-languages-length:876, HImportance:normal
X-HELO:	mout.gmx.net
MIME-Version:	1.0
Message-ID:	<trinity-f19f7555-e19d-4d9b-98bd-3d2da10e8cf1-1506088812465@3c-app-gmx-bs21>
From:	"Joachim Eibl" <Joachim DOT Eibl AT gmx DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Does Cygwin setup modify dlls?
Date:	Fri, 22 Sep 2017 16:00:12 +0200
Sensitivity:	Normal
X-UI-Out-Filterresults:	notjunk:1;V01:K0:noAjGwuGMs8=:6MLdVYeVDQzrcGvv6ZuMH9 Q1fVXmPjQv03C4iOZMjMmzRD/Jb7DqCLPC1zC0EM0+F9eoIy/aX9Ah5allBLoadilknsBVDqw q4us+sKmHWAh7/tPYFgJ1G9LnXtNYidqmiv/nUEiH0p5rya3TlCeXFEok4P0APNwC3Gr026bn sX7ZVg9/Hbckz7nbqMDN3H4AcJ6mEJiFn57HXG1iuq5WDrylUwFVpVTgx244s1xUs3ObnwNw0 bfV7peDqIPJccz4Wx55G7zwdwmyeOTVdz7jttUQv5AqBwGMEhIKdz8//L3Y74H4PLt3dm/ZdI 2Z3Ocx0xxRMNAgo2Mi54xXb7O3TddSG7IBjX6/NYCDUmiywOxx13RHkt8j8jbJGjf0HjzquI3 iaAU94RDk330givwrkIu4Km3CNNXWFw0AbwIIz03OjP7tefjM6F8UB3WQTFpnn39hTVPRK2hV ceMKY5/lq/gyR1QSl4q0uuIZD+2485sVtSinJbzk3PFbgHYAbIt5
X-IsSubscribed:	yes

Hi,
 
In our project we like the Cygwin-Setup tool so much that we use it for our own files too.
Adding our archives to our setup.ini was easy enough and almost everything worked as expected.
 
But then a certain tool didn't work and we found that dll-files that were unpacked by the Cygwin-installer didn't match the files in the archive.
The problem seems to be dll-specific. Other filetypes are not modified.
 
When unpacking using normal Cygwin-tools (tar xf ...) all files were correct. So somehow the installation via Cygwin modifies them.
 
Is this known behaviour? Is this intentional? Can it be turned off? (Is there some postprocessing like "strip" etc?)
Or do you think we have another kind of problem, that is not related to Cygwin?
 
Our Cygwin-setup-version is 2.877, x86_64, running on Windows 10 or Windows 7.
 
Best regards,
Joachim

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