čt 14. 10. 2021 v 15:32 odesílatel Dagfinn Ilmari Mannsåker <ilm...@ilmari.org> napsal: > > Josef Šimánek <josef.sima...@gmail.com> writes: > > > čt 14. 10. 2021 v 15:14 odesílatel Dagfinn Ilmari Mannsåker > > <ilm...@ilmari.org> napsal: > >> > >> Josef Šimánek <josef.sima...@gmail.com> writes: > >> > >> > The only problem I do have currently is auto-detection of perl. I'm > >> > getting error related to missing "Opcode.pm". PERL is autodetected and > >> > enabled (https://pastebin.com/xfRRrDcU). > >> > >> Your Perl (not PERL) installation seems to be incomplete. Opcode.pm is a > >> core module, and should be in /usr/lib64/perl5, judging by the paths in > >> the error message. > >> > >> Which OS is this? Some Linux distributions have separate packages for > >> the interpreter itself and the included modules, and the packages can be > >> named confusingly. E.g. on older Redhat/Fedora versions you have to > >> install the 'perl-core' package to get all the modules, 'perl' is just > >> the interpreter and the bare minimum set of strictily necessary modules. > >> > >> They've fixed this in recent versions (Fedora 34 and Redhat 8, IIRC), so > >> that 'perl' gives you the hole bundle, and 'perl-interpeter' is the > >> minimal one. > > > > I'm using Fedora 34 and I still see perl-Opcode.x86_64 as a separate > > package.` > > Yes, it's a separate package, but the 'perl' package depends on all the > core module packages, so installing that should fix things. You appear > to only have 'perl-interpreter' installed.
You're right. Installing "perl" or "perl-Opcode" manually fixes this problem. Currently I only have "perl-interpreter" installed. > > Anyway it behaves differently with autoconf tools and the meson build > > system. Is perl disabled by default in the current build system? > > configure doesn't auto-detect any optional features, they have to be > explicitly enabled using --with-foo switches. > > - ilmari
