Github messages for voidlinux
 help / color / mirror / Atom feed
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: Wed, 08 Sep 2021 13:11:26 +0200	[thread overview]
Message-ID: <20210908111126.aWLhNnQH6fL1MuzzCOlDtUNbQpA6Byz-fYhzNWbvVoo@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: 1679 bytes --]

New comment by aaFn on void-packages repository

https://github.com/void-linux/void-packages/issues/32857#issuecomment-915142915

Comment:
Correct, I also hear there are performance implications, but primarily related to threads as I get it, not to multiplicity itself (so we already have that impact in). Or let me know if I am wrong.

For now I took 2.0.34 sources from CPAN, recompiled and installed as a second perl instance in /usr/local + redirected by symlink all things like /usr/bin/perl, /usr/bin/cpan, /usr/lib/libperl.so* to my instance in /usr/local - since I cannot remove the perl xbps package because it is required by apache and other packages.

I re-compiled with no thread support at all (`-Uusethreads`), with apache in prefork mode, and with mod_perl built as dynamic module (=> using libperl.so) .. works well 🙂

I find that dual install method a bit awkard though, especially after I found out that whatever order is specified in $PATH, bash seems to always and blindly complete unqualified commands like `perl -v` `to /sbin/perl -v`, therefore bypassing my $PATH order !! (although `which perl` rightfully says `/usr/local/bin/perl` ..) !!
Not sure which mechanism is acting there, but this leaves a bad taste in my mouth.

If you see a better way, let me know.

Else yes, and in support of LAMP on Void Linux https://gist.github.com/adnan360/045d1e4c7619a1e1a9e779d6d35cca92, it would be good to modify our Perl packages with either `-Uusethreads` for no thread at all, or both `-Duseithreads -Dusemultiplicity`, so that it is easy to use mod_perl, and its persistent `ModPerl::Registry / ModPerl::RegistryPrefork` feature for performance.

  parent reply	other threads:[~2021-09-08 11:11 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 [this message]
2021-09-10 16:30 ` leahneukirchen
2021-09-10 17:08 ` aaFn
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=20210908111126.aWLhNnQH6fL1MuzzCOlDtUNbQpA6Byz-fYhzNWbvVoo@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).