Installation of Crypt module issue

rpike has asked for the wisdom of the Perl Monks concerning the following question:

I followed the steps as outlined on this page http://www.perlmonks.org/?node_id=128077 and got through it fine. What are the next steps I need to follow? Do I need to move any files out of the temp directory it suggests creating to put everything in from the start? Set up any paths? Etc..,? Thanks.

Comment on Installation of Crypt module issue

Replies are listed 'Best First'.
Re: Installation of Crypt module issue by almut (Canon) on Jan 20, 2010 at 21:05 UTC
In case the last step of the build process (i.e. `make install`) was successful, you no longer need the temp directory, so feel free to delete it. Whether you need to set up any paths etc. depends on where you installed it to, and on the details of the particular module. For example, if the module depends on a third party library, and the respective shared object(s) have been installed in a non-standard location, you might need to set up/adjust shared library search paths. But why not just try and see if it loads properly? In many cases, a simple `$ perl -MCrypt::Whatever -e1` [download] will do (i.e., if you get no error, everything is fine). (There are also modules which load some parts at run-time (on demand); for those you'd in theory need to write a little test script that exercises all required functionality, in order to tell if things are in fact set up properly...)	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Installation of Crypt module issue
by almut (Canon) on Jan 20, 2010 at 21:05 UTC

In case the last step of the build process (i.e. make install) was successful, you no longer need the temp directory, so feel free to delete it.

Whether you need to set up any paths etc. depends on where you installed it to, and on the details of the particular module. For example, if the module depends on a third party library, and the respective shared object(s) have been installed in a non-standard location, you might need to set up/adjust shared library search paths.

But why not just try and see if it loads properly? In many cases, a simple

$ perl -MCrypt::Whatever -e1
[download]

will do (i.e., if you get no error, everything is fine). (There are also modules which load some parts at run-time (on demand); for those you'd in theory need to write a little test script that exercises all required functionality, in order to tell if things are in fact set up properly...)

[reply]
[d/l]
[select]