Re^2: Questions about mod_perl modules and dependencies.

Sorry for answering late.
2) @INC is an array with paths where perl is looking for modules. As far as I know @INC is set to the system default perl (let's call it "system-perl" for now). So if I would install a second perl (let's call it "rh-perl") on my linux it would install perl under /opt/rh-perl/5.xx.x, how does this affect @INC? Would @INC still show the system-perl paths instead of my rh-perl paths? Would it show both paths?
I'd assume each perl version got a different @INC array. system-perl got different path's in it then rh-perl does. So if I would compile mod_perl with rh-perl @INC for mod_perl then would be the new rh-perl paths, right?

Even Rocky 8 is totally fine for me. It's just for an proof of concept where I need perl. The original vm used to be CentOS7 which had perl 5.16.3 which doesn't work for this task.

Comment on Re^2: Questions about mod_perl modules and dependencies.

Replies are listed 'Best First'.
Re^3: Questions about mod_perl modules and dependencies. by hippo (Archbishop) on Apr 04, 2022 at 12:52 UTC
Each perl binary will have its own @INC and IIRC the mod_perl that you build using that perl binary inherits the @INC from it. However, the @INC which any particular mod_perl installation starts with can always be modified in the configuration afterwards so it is not the be all and end all to get it right first time. 🦛	[reply]
Re^4: Questions about mod_perl modules and dependencies. by feumw (Sexton) on Apr 05, 2022 at 05:40 UTC
Thank you sir.	[reply]