From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: How to get GNU Parallel working with Cygwin
Date: Fri, 17 Mar 2017 19:23:00 -0000 [thread overview]
Message-ID: <874lyrwvuz.fsf@Rainer.invalid> (raw)
In-Reply-To: <58CB08FE.4060000@gmail.com> (Matt D.'s message of "Thu, 16 Mar 2017 17:51:58 -0400")
Matt D. writes:
> I noticed today that we don't have this package.
"We" don't have this package because it can't work correctly on Cygwin
in certain circumstances (see below) and upstream didn't want to change
the way semaphores work to accomodate this situation.
> I tried building it
> from source with a './configure && make && make install'.
>
> But when I run "sem" I get the following output:
>
> 1 [main] perl 7712 child_info_fork::abort: address space needed by
> 'Util.dll' (0x1E0000) is already occupied
> 1 [main] perl 13596 child_info_fork::abort: address space needed by
> 'Util.dll' (0x1E0000) is already occupied
> 1 [main] perl 13920 child_info_fork::abort: address space needed by
> 'Util.dll' (0x1E0000) is already occupied
> ...
>
> I don't have any issue running perl directly.
That's most likely List::Util colliding with some other DLL or getting
intercepted by BLODA.
> The package in question:
> https://www.gnu.org/software/parallel/
You'll either need to rebase all XS modules it installed manually or
install them from setup.exe before installing parallel. Note that
parallel can't work correctly when your home is on a file system with
ustable inodes and thus can't refcount hardlinks.
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
prev parent reply other threads:[~2017-03-17 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 21:52 Matt D.
2017-03-17 2:19 ` Ken Brown
2017-03-17 19:23 ` 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=874lyrwvuz.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).