From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Perl child_info_fork runtime error
Date: Wed, 30 May 2018 22:05:00 -0000 [thread overview]
Message-ID: <878t80vrwn.fsf@Rainer.invalid> (raw)
In-Reply-To: <20180530105709.GA12768@rus.uni-stuttgart.de> (Ulli Horlacher's message of "Wed, 30 May 2018 12:57:09 +0200")
Ulli Horlacher writes:
> Line 106 in /client/bin/fexsend is:
That path looks suspiciously like something not properly packaged for
Cygwin. If so, it may use DLL that are not rebased and collide with
Cygwin's.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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:[~2018-05-30 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 11:59 Ulli Horlacher
2018-05-30 22:05 ` Achim Gratz [this message]
2018-06-04 9:23 ` Ulli Horlacher
2018-06-04 19:24 ` Achim Gratz
2018-06-06 15:31 ` Ulli Horlacher
2018-06-06 15:49 ` Marco Atzeri
2018-06-06 16:49 ` Ulli Horlacher
2018-07-09 0:41 ` Ulli Horlacher
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=878t80vrwn.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).