Hello Michael,
I had hoped to have a nice FAQ written up by now, but it's not quite ready for general consumption. Hopefully I can help you out with some of the basics in this post. I have been in a very similar situation before (read the gory details here:
http://www.aota.net/ubb/Forum3/HTML/001515-1.html)
First, I notice that you specifically ask for Crypt::SSLeay.
What I am about to say is based on correspondence with Terra concerning the SSLeay module. Terra is working on it, but it hasn't been maintained in a while and doesn't quite work with the current (as of when I inquired) implementation of the https protocol on the FutureQuest servers. Hopefully this will not take too long to get working together, but no guarantee has been made of it ever getting installed. Obviously Terra is a better person to update you on the progress than I am.
The integration between the Crypt::SSLeay module and https may mean that even if you manage to get this module successfully installed locally (which is what you want to do), it may break when you actually use it. Query
http://service.futurequest.net/tech/support for the term "module" and click the first solution to learn how to find out whether a module has been installed or not.
FutureQuest will generally install modules from the CPAN library for you, if you ask. However, custom modules must be installed by you. If you are installing a Perl program/ module from a Makefile, you want to do a local installation. Makefiles generally assume that you have root access, which is why you are getting the permission violation errors. To specify that you want to install into a directory that you DO have permission to, take the following steps (> indicates command prompt):
Code Sample: >perl Makefile.PL PREFIX=/big/dom/xACCOUNT <ENTER>
where ACCOUNT is specific to your directory.
>make
>make test
|
|
This step should be successful. If it is not, there is not much point proceeding to the next step. Things can get complex if you have to troubleshoot. If you do have problems, please post them.
Code Sample:
The program/ module should now be installed in your local directory. You can define a subdirectory by altering the PREFIX, but I have found that some modules don't install properly in a subdirectory.
Assuming that all the above went well, you now have to modify your scripts that use the module to look for the module in your local directory. To do this, add the following statement to the beginning of any CGI scripts requiring the custom installed module.
Code Sample: use lib '/big/dom/xwebspacecreations/lib/perl5/site_perl/5.005/i686-linux/';
|
|
NOTE: You may need to modify the path if your module has been installed in a slightly different location. To find out whether the path is right, telnet to your account, cd to the directory containing your modified CGI script (i.e. cgi-bin or cgi-ssl), then type 'perl test.cgi' (without the quotes) where test.cgi is the name of your modified script. If you get an error saying the the module couldn't be found in your @INC list of paths, you will need to modify the path in your script.
This is general advice and if you can't get Crypt::SSLeay and LWP installed (they don't appear to currently be installed), it is doubtful that even if you get the other custom module installed locally that your script will work. If you need this script NOW, you may be better off looking for an easier to implement solution.
If anyone sees any errors/ has any corrections to this general advice for a local installation, please add them to this thread.
Good luck,
Matt
P.S. Check out
http://www.aota.net/ubb/Forum3/HTML/001070-1.html for new info on SSLeay.
[This message has been edited by Matt (edited 03-30-01@3:16 pm)]
Linear Mode
