This is the mail archive of the
mailing list for the Cygwin project.
Re: Does Cygwin setup modify dlls?
- From: Marco Atzeri <marco dot atzeri at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 22 Sep 2017 16:46:48 +0200
- Subject: Re: Does Cygwin setup modify dlls?
- Authentication-results: sourceware.org; auth=none
- References: <trinity-f19f7555-e19d-4d9b-98bd-3d2da10e8cf1-1506088812465@3c-app-gmx-bs21> <email@example.com>
On 22/09/2017 16:11, Eliot Moss wrote:
On 9/22/2017 10:00 AM, Joachim Eibl wrote:
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
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
$ rebase -si |grep /usr/bin/cygglpk-40.dll
base 0x0003e1710000 size 0x000ec000
To perform a proper fork all the dlls should be loaded
at not colliding address
This activity is performed by the script
after the files installation.
Regards - Eliot Moss
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple