From: aaFn <aaFn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: How to reconfigure perl on Void Linux - Or is there a perl-devel package ?
Date: Fri, 10 Sep 2021 19:08:34 +0200 [thread overview]
Message-ID: <20210910170834.eWsbsQK042_XdQAeArq-7UXBVnkOyXm-zTqWUJnR-nk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32857@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
New comment by aaFn on void-packages repository
https://github.com/void-linux/void-packages/issues/32857#issuecomment-917067470
Comment:
Yes, I checked already. This is why I came here 😁 :
Agree with you that https://perl.apache.org/docs/2.0/user/install/install.html#Prerequisites is ambiguous and seems to state that they don't care ...
But fact is that the command
`perl Makefile.PL MP_APXS=/usr/bin/apxs MP_APR_CONFIG=/sbin/apr-1-configMP_AP_CONFIGURE="--with-mpm=prefork"
`
does fail, with the error message I copied in my initial post at top, with that somewhat cryptic message. To make sure I opened their make generation code, and could confirm they want either none, or both, but not one of them.
And when I do (to force NO_THREADS)
`perl Makefile.PL MP_APXS=/usr/bin/apxs MP_APR_CONFIG=/sbin/apr-1-config MP_NO_THREADS=1 MP_AP_CONFIGURE="--with-mpm=prefork"`
that fails also in the same way ... so no choice but to recompile Perl with either none or both ... and I don't dare to touch their code to force things, as I am not sure of what is checked at later steps + things do not seem to be coded in a robust way on that side.
next prev parent reply other threads:[~2021-09-10 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 14:41 [ISSUE] " aaFn
2021-09-08 9:51 ` leahneukirchen
2021-09-08 11:11 ` aaFn
2021-09-10 16:30 ` leahneukirchen
2021-09-10 17:08 ` aaFn [this message]
2021-09-10 17:25 ` leahneukirchen
2021-09-10 18:05 ` aaFn
2021-09-11 15:28 ` aaFn
2022-06-05 2:14 ` github-actions
2022-06-07 11:45 ` leahneukirchen
2022-06-07 12:55 ` aaFn
2022-09-06 2:16 ` github-actions
2022-09-06 9:24 ` leahneukirchen
2022-10-01 15:04 ` [ISSUE] [CLOSED] " leahneukirchen
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=20210910170834.eWsbsQK042_XdQAeArq-7UXBVnkOyXm-zTqWUJnR-nk@z \
--to=aafn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).