From: Mark H Weaver <mhw@netris.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 31216@debbugs.gnu.org
Subject: bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error
Date: Sat, 21 Apr 2018 01:04:33 -0400 [thread overview]
Message-ID: <87vaclxi8u.fsf@netris.org> (raw)
In-Reply-To: <87zi1xxmh8.fsf@netris.org> (Mark H. Weaver's message of "Fri, 20 Apr 2018 23:33:07 -0400")
Unfortunately, the compatibility symlinks are not sufficient. The
problem is that other perl packages such a po4a are installing their
modules into $out/lib/perl5/site_perl/5.26.1, which conflicts with the
compatibility symlink that we're installing in perl.
When perl and po4a are put together into a profile, po4a has a directory
<PO4A>/lib/perl5/site_perl/5.26.1 and perl has its compatibility symlink
in the same relative location. The (guix build union) code follows
perl's symlink to its target directory <PERL>/lib/perl5/site_perl/5.26.2
and merges that with <PO4A>/lib/perl5/site_perl/5.26.1 to form
<PROFILE>/lib/perl5/site_perl/5.26.1, but that not in any of the paths.
I'm now trying a different approach: hack the replacement perl to think
it is version 5.26.1, although it is actually 5.26.2. I'll report back
soon.
Mark
next prev parent reply other threads:[~2018-04-21 5:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 3:14 bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error George myglc2 Clemmer
2018-04-19 14:39 ` Leo Famulari
2018-04-20 12:41 ` Julien Lepiller
2018-04-20 23:46 ` Leo Famulari
2018-04-20 23:51 ` Leo Famulari
2018-04-21 3:15 ` Mark H Weaver
2018-04-21 3:33 ` Mark H Weaver
2018-04-21 5:04 ` Mark H Weaver [this message]
2018-04-21 5:24 ` Mark H Weaver
2018-04-22 17:42 ` Leo Famulari
2018-04-25 1:36 ` Mark H Weaver
2018-04-25 13:34 ` myglc2
2018-04-26 10:54 ` Marius Bakke
2018-04-26 12:51 ` George myglc2 Clemmer
2018-04-19 16:06 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vaclxi8u.fsf@netris.org \
--to=mhw@netris.org \
--cc=31216@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).