On Monday 11 March 2019 16:42:21 Pete Biggs wrote:> I'm afraid I'm not expert on these things - I tend to do the naughty > thing of using CPAN to install in system locations!Hi Peter, Do you have any instructiions on how to do this? I realise it's far from ideal, but I need to get this system working, and can do it on a stand alone server.> > But I think the .spec file generated, or the variables used for the > > > it is trying to package ..../usr/share/ > > I think you need the help of someone who knows about .spec files! >I did wonder if maybe my rpmbuild spec is wrong as every RPM I'm trying to create is looking in the wrong location for the man pages, and the perl module files. I commented out the line for the man pages, but can't comment out the perl modules :)
> > Do you have any instructiions on how to do this? I realise it's far from > ideal, but I need to get this system working, and can do it on a stand alone > server.It's a long time since I've done it, but I think CPAN puts some variables in your .bashrc to configure the process. First you should run 'perl -V' to see if there are any entries that aren't the system wide location - you are looking for the @INC path and/or variables like $PERL_LOCAL_LIB_ROOT If they are ok, at the CPAN prompt do 'o conf' to see what CPAN thinks the config is - I think the crucial options are the ones that start "mbuild_". Ultimately you can redo the CPAN config by 'o conf init'.> > > But I think the .spec file generated, or the variables used for the > > > > > > it is trying to package ..../usr/share/ > > > > I think you need the help of someone who knows about .spec files! > > > > I did wonder if maybe my rpmbuild spec is wrong as every RPM I'm trying to > create is looking in the wrong location for the man pages, and the perl > module files. I commented out the line for the man pages, but can't comment > out the perl modules :)The build and locations are influenced by some environment variables setup by rpmbuild - I have a feeling that the perl build process is using different locations to the rpmbuild so everything is getting confused. P.
On 3/11/19 9:53 AM, Gary Stainburn wrote:> On Monday 11 March 2019 16:42:21 Pete Biggs wrote: >> I'm afraid I'm not expert on these things - I tend to do the naughty >> thing of using CPAN to install in system locations! > Hi Peter, > > Do you have any instructiions on how to do this? I realise it's far from > ideal, but I need to get this system working, and can do it on a stand alone > server. > >> But I think the .spec file generated, or the variables used for the >> >> >> it is trying to package ..../usr/share/ >> >> I think you need the help of someone who knows about .spec files! >> > I did wonder if maybe my rpmbuild spec is wrong as every RPM I'm trying to > create is looking in the wrong location for the man pages, and the perl > module files. I commented out the line for the man pages, but can't comment > out the perl modules :) > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centosWhat often happens when you have "larger" modules, they reply on libraries.? To build the perl module from source, you need to devel rpm of the library installed to link against. example libxml2-2.7.6-21.el6_8.1.x86_64 libxml2-devel-2.7.6-21.el6_8.1.x86_64 XML::Simple won't build unless the devel is present CPAN isn't real good at reporting why the build failed, just that it failed. What I've learned to? do when I have this sort of issue is to pop out of CPAN and into ~/.cpan/build. Locate the unpacked module and try the build manually. I get better errors that way.>
On Mar 11, 2019, at 6:16 PM, Bruce Ferrell <bferrell at baywinds.org> wrote:> > What I've learned to do when I have this sort of issue is to pop out of CPAN and into ~/.cpan/build.If you mean that you do that manually, you don?t have to. The ?look? command in the cpan shell or the --look option to cpanm does that automatically. That is, it unpacks the module and drops you into a sub-shell where you can work with the module manually. Back when I still had to support CentOS 5, I?d occasionally have to do this to get some modules to build because they required local edits or configuration overrides that the upstream developers didn?t want to support, its Perl being deemed too old to bother with any more.