Re^2: Personal library with CPAN

That seems to work great. But then while installing DBI it dies with the following error

/usr/local/bin/perl -p -e "s/~DRIVER~/Perl/g" ./Driver.xst > Perl.xsi
/usr/local/bin/perl /usr/local/lib/perl5/5.8.0/ExtUtils/xsubpp  -typem
+ap /usr/local/lib/perl5/5.8.0/ExtUtils/typemap -typemap typemap  Perl
+.xs > Perl.xsc && mv Perl.xsc Perl.c
cc -c    -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.0/BSDPAN" -DHAS_FPSET
+MASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -I/usr/local/include 
+-O -pipe    -DVERSION=\"1.50\"  -DXS_VERSION=\"1.50\" -DPIC -fPIC "-I
+/usr/local/lib/perl5/5.8.0/mach/CORE"  -W -Wall -Wpointer-arith -Wbad
+-function-cast -Wno-comment -Wno-sign-compare -Wno-cast-qual -DDBI_NO
+_THREADS Perl.c
cc: permission denied
*** Error code 126

Stop in /usr/home/sites/www.whereever.com/whereever/.cpan/build/DBI-1.
+50.
  /usr/bin/make  -- NOT OK
Running make test
  Can't test without successful make
Running make install
  make had returned bad status, install seems impossible
[download]

I'll continue to search perlmonks, but i think this might just be a permission setting that is obvious to real unix hackers ;)

___________
Eric Hodges

Comment on Re^2: Personal library with CPAN Download Code

Replies are listed 'Best First'.
Re^3: Personal library with CPAN by Zaxo (Archbishop) on Mar 10, 2006 at 21:15 UTC
Yes, that appears to be a permission problem with `-DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.0/BSDPAN"`. If you need a private cpan directory, you probably don't have write permission there. I don't know if this is the source of the problem, but sometimes authors hardcode paths that they should let CPAN.pm figure out. You could try setting and exporting APPLIB_EXP before the build as a workaround. After Compline, Zaxo	[reply]

Replies are listed 'Best First'.

Re^3: Personal library with CPAN
by Zaxo (Archbishop) on Mar 10, 2006 at 21:15 UTC

Yes, that appears to be a permission problem with -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.0/BSDPAN". If you need a private cpan directory, you probably don't have write permission there.

I don't know if this is the source of the problem, but sometimes authors hardcode paths that they should let CPAN.pm figure out. You could try setting and exporting APPLIB_EXP before the build as a workaround.

After Compline,
Zaxo

[reply]