From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Does Cygwin setup modify dlls?
Date: Sat, 23 Sep 2017 19:53:00 -0000 [thread overview]
Message-ID: <87zi9ldwee.fsf@Rainer.invalid> (raw)
In-Reply-To: <trinity-f19f7555-e19d-4d9b-98bd-3d2da10e8cf1-1506088812465@3c-app-gmx-bs21> (Joachim Eibl's message of "Fri, 22 Sep 2017 16:00:12 +0200")
Joachim Eibl writes:
> 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.
Anything that is packaged will be rebased by the _autorebase postinstall
script (by default just DLL, but you can also arrange for some PE falgs
to be set on executables). Currently the handful of exceptions needed
within Cygwin are hard-coded into the rebase_pkg function, so you'll
have to patch that.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
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
prev parent reply other threads:[~2017-09-23 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 14:00 Joachim Eibl
2017-09-22 14:11 ` Eliot Moss
2017-09-22 14:46 ` Marco Atzeri
[not found] ` <trinity-4204847c-6bba-4606-b43c-8b376b96a945-1506094235587@3c-app-gmx-bs22>
2017-09-22 15:31 ` Joachim Eibl
2017-09-22 16:49 ` Marco Atzeri
2017-09-27 4:50 ` Andrey Repin
2017-09-27 10:04 ` Joachim Eibl
2017-09-22 15:49 ` Eliot Moss
2017-09-23 19:53 ` Achim Gratz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zi9ldwee.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).