This is the mail archive of the
mailing list for the Cygwin project.
Re: Does Cygwin setup modify dlls?
- From: Eliot Moss <moss at cs dot umass dot edu>
- To: cygwin at cygwin dot com
- Date: Fri, 22 Sep 2017 10:11:07 -0400
- 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>
- Reply-to: moss at cs dot umass dot edu
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 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.
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.
Regards - Eliot Moss
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple