From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 46758 invoked by alias); 22 Sep 2017 15:49:23 -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 46749 invoked by uid 89); 22 Sep 2017 15:49:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=his, our, HContent-Transfer-Encoding:8bit X-HELO: mailsrv.cs.umass.edu Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Sep 2017 15:49:21 +0000 Received: from [192.168.24.205] (eduroamgw.cs.umass.edu [128.119.40.194]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 27865401C1B2; Fri, 22 Sep 2017 11:49:20 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Does Cygwin setup modify dlls? To: cygwin@cygwin.com References: <0ec4a5bf-d608-68d2-973d-3e8b5db33589@cs.umass.edu> <16302f48-6e7c-7af2-6a2e-15091794769a@gmail.com> From: Eliot Moss Message-ID: <4eb6dfac-1995-212b-4d9b-940c091f34b6@cs.umass.edu> Date: Fri, 22 Sep 2017 15:49:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <16302f48-6e7c-7af2-6a2e-15091794769a@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00211.txt.bz2 On 9/22/2017 10:46 AM, Marco Atzeri wrote: > On 22/09/2017 16:11, Eliot Moss wrote: >> On 9/22/2017 10:00 AM, Joachim Eibl wrote: >>> 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. > >> >> Cygwin's rebasing of DLLs does modify the files (slightly). >> Others can probably detail the exact nature of what changes, >> and perhaps the comparison tool can be refined to ignore that >> as a difference. > > the change is on ImageBase address > > $ objdump -x /usr/bin/cygglpk-40.dll |grep ImageBase > ImageBase               00000003e1710000 So, if the OP compared output of objdump ignoring the ImageBase difference, would that be able to indicate that the DLL is "the same" for his purposes of knowing whether an installation is equivalent in terms of versions, releases, etc.? EM -- 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