You seem to be right. However, I have installed a number of modules with this prefix using CPANP w/o problem. I have this in .bashrc:
export MODULEBUILDRC="/home/salmonix/perl5/.modulebuildrc" export PERL_MM_OPT="INSTALL_BASE=/home/salmonix/perl5" export PERL5LIB="/home/salmonix/perl5/lib/perl5/x86_64-linux-thread-multi:/home/salmonix/perl5/lib/perl5" export PATH="/home/salmonix/perl5/bin:$PATH" export MANPATH="/home/salmonix/perl5/man:$MANPATH" Shall I export install_base too? On Wed, Aug 11, 2010 at 9:36 PM, Mattia Barbon <mattia.bar...@libero.it>wrote: > Laslo Forro wrote: > >> Found at >> /home/salmonix/perl5/lib/perl5/x86_64-linux-thread-multi/Alien/wxWidgets/Config >> - attached. >> > > I think (hope...) the problem is a misuse of install_base/prefix. The > supported way is: > > $ perl Build.PL --install_base /home/foo > $ ./Build > $ ./Build install > > Using destdir/prefix or passing install_base after Build.PL time is not > supported. > > > Hmmm, there is also an Alien/wxWidgets path at >> /home/salmonix/perl5/lib/perl5/Alien/wxWidgets , w/o the config file. This >> directory contains only Utility.pm... >> > > This is correct, because wxWidgets.pm and Utility.pm are arch-independent. > > Regards, > Mattia > >
