From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88315 invoked by alias); 22 Sep 2017 14:00:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 78159 invoked by uid 89); 22 Sep 2017 14:00:26 -0000 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 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.18) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Sep 2017 14:00:16 +0000 Received: from [80.246.32.33] by 3c-app-gmx-bs21.server.lan (via HTTP); Fri, 22 Sep 2017 16:00:12 +0200 MIME-Version: 1.0 Message-ID: From: "Joachim Eibl" To: cygwin@cygwin.com Subject: Does Cygwin setup modify dlls? Content-Type: text/plain; charset=UTF-8 Date: Fri, 22 Sep 2017 14:00:00 -0000 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 X-SW-Source: 2017-09/txt/msg00207.txt.bz2 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