Hi folks,
Each time starting cpan it asks to reconfig cpan; # perl -MCPAN -e shell Sorry, we have to rerun the configuration dialog for CPAN.pm due to some missing parameters... Normally CPAN.pm keeps config variables in memory and changes need to be saved in a separate 'o conf commit' command to make them permanent between sessions. If you set the 'auto_commit' option to true, changes to a config variable are always automatically committed to disk. <auto_commit> Always commit changes to config variables to disk? [no] [Enter] A Build.PL is run by perl in a separate process. Likewise we run './Build' and './Build install' in separate processes. If you have any parameters you want to pass to the calls, please specify them here. Typical frequently used settings: --install_base /home/xxx # different installation directory <mbuildpl_arg> Parameters for the 'perl Build.PL' command? [] [Enter] Parameters for the './Build' command? Setting might be: --extra_linker_flags -L/usr/foo/lib # non-standard library location <mbuild_arg> Your choice: [] [Enter] Do you want to use a different command for './Build install'? Sudo users will probably prefer: su root -c ./Build or sudo ./Build or /path1/to/sudo -u admin_account ./Build <mbuild_install_build_command> or some such. Your choice: [./Build] [Enter] Parameters for the './Build install' command? Typical frequently used setting: --uninst 1 # uninstall conflicting files <mbuild_install_arg> Your choice: [] [Enter] Please remember to call 'o conf commit' to make the config permanent! cpan shell -- CPAN exploration and modules installation (v1.9301) ReadLine support enabled cpan[1]> It start "cpan[1]>" instead. Please advise how to fix this problem. TIA B.R. Stephen L Send instant messages to your online friends http://uk.messenger.yahoo.com