From: "Joachim Eibl" <Joachim.Eibl@gmx.de>
To: cygwin@cygwin.com
Subject: Re: Re: Does Cygwin setup modify dlls?
Date: Wed, 27 Sep 2017 10:04:00 -0000 [thread overview]
Message-ID: <trinity-02fc9973-eeb4-4b9b-9829-92440c40b9a2-1506506634914@3c-app-gmx-bs70> (raw)
In-Reply-To: <1245656876.20170927073928@yandex.ru>
Thanks for all answers.
We will patch /usr/bin/rebaselst and extend the sed-expression in function rebase_pkg()
by adding another exception to the existing ones:
sed -e '/\(cygwin1\|cyglsa.*\)\.dll$/d' \
-e '/\/\(d\?ash|rebase\|peflags\)\.exe$/d' \
-e '/\/octave\//!{/\(mex\|oct\)$/d}' \
-e '/gnuplot\/demo\/plugin\/.*\.so/d' \
-e '/^\/usr\/lib\/ocaml\/.*\.so/d' \
-e '/sys-root\/mingw/d' \
+ -e '/our-subdir/d' \
-e 's/^/\//' \
>>"${g}"
> > Is there a possibility to avoid the rebasing, e.g. for certain folders?
> > In my case the intention was to use the Cygwin installer only, but the
> > files in the package are not dependent on cygwin libraries. So forking is not an issue.
> He did mean fork(2) call, not a "source code fork".
> DLL rebase is necessary for Cygwin to run in first place.
I understood this. The tools we install aren't run in a cygwin-context.
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
next prev parent reply other threads:[~2017-09-27 10:04 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 [this message]
2017-09-22 15:49 ` Eliot Moss
2017-09-23 19:53 ` Achim Gratz
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=trinity-02fc9973-eeb4-4b9b-9829-92440c40b9a2-1506506634914@3c-app-gmx-bs70 \
--to=joachim.eibl@gmx.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).