|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
perl module installation problems... experts advice needed,...
Post 92186 by cbkihong on Thursday 8th of December 2005 08:35:16 AM
12-08-2005
There are indeed "standard" procedures.
On Unix systems, downloading the tarball, run "perl Makefile.PL" and then "make", "make test", "make install" (mostly as root)is the standard procedure. If there is errors, that usually implies some problems. For instance, for modules that have native (C) parts, that may mean missing 3rd party libraries, incompatibility or if the failure is with the tests, then assuming the tests are well maintained, it is likely to indicate the module may not work on your machine.
You can also use the CPAN module and the "cpan" shell to install modules. Pretty much an automation of the download, extract, compile and install phase. But as it is just using the same tarball, if you have problems with the manual installation you are likely to come into the same kind of problems with this. But most of the time, it is simple and reliable.
A past member has kindly written an introduction here:
https://www.unix.com/tips-and-tutorials/14246-perl-cpan-intro-newbies.html
Windows ActiveState distribution has packaged modules similar to that of CPAN, but not as complete. Use the "ppm" for the interface. If provided, any native components are already compiled so you don't need the compiler (MS VC++ Compiler). If this fails, for non-compiled module you can then copy files as your friend did (it is correct, and I do this too to put custom modules together with my project sources in order to avoid relying on systemwide offerings. But if there are compiled parts, then this trick won't work.Either you need an MS VC++ compiler (because ActiveState Perl is compiled with this compiler), or download mingw and compile Perl from sources with it, and then any custom modules you download.
So in my opinion, Windows is not a good environment for Perl development as there are too many compiled Perl modules nowadays.
What is the error? And how did you install it?
If you understand how the Perl require mechanism, then you should be pretty comfortable with this. As I said, I seldom install custom modules systemwide (except for compiled ones) to avoid transferring the sources to another machine just to find that the dependencies aren't installed. So simpler modules, it is better to put them locally rather than systemwide, and then set the @INC or 'use lib' to point to where the modules are. Most sophisticated Perl scripts do this. So it's normal.
On Unix systems, downloading the tarball, run "perl Makefile.PL" and then "make", "make test", "make install" (mostly as root)is the standard procedure. If there is errors, that usually implies some problems. For instance, for modules that have native (C) parts, that may mean missing 3rd party libraries, incompatibility or if the failure is with the tests, then assuming the tests are well maintained, it is likely to indicate the module may not work on your machine.
You can also use the CPAN module and the "cpan" shell to install modules. Pretty much an automation of the download, extract, compile and install phase. But as it is just using the same tarball, if you have problems with the manual installation you are likely to come into the same kind of problems with this. But most of the time, it is simple and reliable.
A past member has kindly written an introduction here:
https://www.unix.com/tips-and-tutorials/14246-perl-cpan-intro-newbies.html
Windows ActiveState distribution has packaged modules similar to that of CPAN, but not as complete. Use the "ppm" for the interface. If provided, any native components are already compiled so you don't need the compiler (MS VC++ Compiler). If this fails, for non-compiled module you can then copy files as your friend did (it is correct, and I do this too to put custom modules together with my project sources in order to avoid relying on systemwide offerings. But if there are compiled parts, then this trick won't work.Either you need an MS VC++ compiler (because ActiveState Perl is compiled with this compiler), or download mingw and compile Perl from sources with it, and then any custom modules you download.
So in my opinion, Windows is not a good environment for Perl development as there are too many compiled Perl modules nowadays.
Quote:
Originally Posted by sekar sundaram
----------
when i tried to install xml::simple and xml:
arser
there was an error.
when i tried to install xml::simple and xml:
arserthere was an error.
Quote:
"there may be some standard procedures one should follow while installing modules and etc.. even though if we do like copying it might work..but after sometime it may give some problems.."
Last edited by cbkihong; 12-08-2005 at 09:40 AM..
|
|
9 More Discussions You Might Find Interesting
1. Programming
how can i check my code with lint? What if the code containes multiple module? The check is been done on each module separately?
What is the command to use the lint
Any relevant site???
Thanks a lot. You are doing a great job.:cool: (2 Replies)
Discussion started by: amatsaka
2 Replies
2. Shell Programming and Scripting
Hi,
I've a issue in writing a perl script that will automatically monitor the site availability.
There are two different cookies are set in two consecutive flows to a URL and this second cookie has to be passed to the third step which actually gives permission to access based upon the cookie. ... (1 Reply)
Discussion started by: dayanandra
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
I am trying to install perl modules in HPUX under my account. I do not have the root permission.
The module name I am trying to install is Spreadsheet-WriteExcel. I have downloaded the tar.gz file from CPAN and extracted the same under my home directory.
When I try do 'perl... (2 Replies)
Discussion started by: sabyasm
2 Replies
4. Shell Programming and Scripting
Hi All,
I am failry new to Perl.I am trying to install a Perl module (Filesys::df.pm) in an IBM AIX5.3 server.But I could not succeed in that.I am getting the following error:
abcd3dev# make
cc_r -c -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem=16384 -qnoansialias... (6 Replies)
Discussion started by: surjithss
6 Replies
5. UNIX for Dummies Questions & Answers
Where to start... I am a system administrator who didn't think he would ever be one. My first work was on Window 2000 as a tech(hardware, installs, stuff like that). Then we got Macs (I work in photography and Videography). The I was sent to Mac cert school. Set up a Mac Xserve and about 100... (2 Replies)
Discussion started by: Squidy P
2 Replies
6. Windows & DOS: Issues & Discussions
Hi,
I am struggling in installing TK module for strawberry perl.
I downloaded TK804 module,
extracted to a folder, kept in c:/strawberry/perl/lib path,
then from tht path
1) perl makefile.pl
2)dmake
3)dmake test
4)dmake install
During perl makefile.pl it is giving error as... (3 Replies)
Discussion started by: vasanth.vadalur
3 Replies
7. Shell Programming and Scripting
Hi 'm getting error while installing perl mdule on linux.can any one tell me how to resolve that error?
problem is:
CPAN: File::Temp loaded ok (v0.22)
CPAN.pm: Going to build J/JD/JDB/Win32-OLE-0.1709.tar.gz
OS unsupported
Warning: No success on command
Warning (usually harmless):... (1 Reply)
Discussion started by: kavi.mogu
1 Replies
8. Shell Programming and Scripting
I have issue with the perl module installed in the new Linux server
I have installed the required module, but still the perl program was not able to find the path
I'm getting the below error:
Can't locate Log/Log4perl.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/Log4perl.pm... (5 Replies)
Discussion started by: help_scr_seeker
5 Replies
9. Shell Programming and Scripting
Hi all,
I have written a wrapper script in Perl which will be used on AIX, Linux and Windows and I do not want to change any code for the needs for a specific OS if avoidable.
It works fine so far on all 3 OSes, not blowing up any stacks any more, but I am unsure how to handle writing log files... (7 Replies)
Discussion started by: zaxxon
7 Replies
LEARN ABOUT MOJAVE
perlnetware
PERLNETWARE(1) Perl Programmers Reference Guide PERLNETWARE(1) NAME
perlnetware - Perl for NetWare DESCRIPTION
This file gives instructions for building Perl 5.7 and above, and also Perl modules for NetWare. Before you start, you may want to read the README file found in the top level directory into which the Perl source code distribution was extracted. Make sure you read and understand the terms under which the software is being distributed. BUILD
This section describes the steps to be performed to build a Perl NLM and other associated NLMs. Tools & SDK The build requires CodeWarrior compiler and linker. In addition, the "NetWare SDK", "NLM & NetWare Libraries for C" and "NetWare Server Protocol Libraries for C", all available at <http://developer.novell.com/wiki/index.php/Category:Novell_Developer_Kit>, are required. Microsoft Visual C++ version 4.2 or later is also required. Setup The build process is dependent on the location of the NetWare SDK. Once the Tools & SDK are installed, the build environment has to be setup. The following batch files setup the environment. SetNWBld.bat The Execution of this file takes 2 parameters as input. The first being the NetWare SDK path, second being the path for CodeWarrior Compiler & tools. Execution of this file sets these paths and also sets the build type to Release by default. Buildtype.bat This is used to set the build type to debug or release. Change the build type only after executing SetNWBld.bat Example: 1. Typing "buildtype d on" at the command prompt causes the buildtype to be set to Debug type with D2 flag set. 2. Typing "buildtype d off" or "buildtype d" at the command prompt causes the buildtype to be set to Debug type with D1 flag set. 3. Typing "buildtype r" at the command prompt sets it to Release Build type. Make The make process runs only under WinNT shell. The NetWare makefile is located under the NetWare folder. This makes use of miniperl.exe to run some of the Perl scripts. To create miniperl.exe, first set the required paths for Visual c++ compiler (specify vcvars32 location) at the command prompt. Then run nmake from win32 folder through WinNT command prompt. The build process can be stopped after miniperl.exe is created. Then run nmake from NetWare folder through WinNT command prompt. Currently the following two build types are tested on NetWare: o USE_MULTI, USE_ITHREADS & USE_IMP_SYS defined o USE_MULTI & USE_IMP_SYS defined and USE_ITHREADS not defined Interpreter Once miniperl.exe creation is over, run nmake from the NetWare folder. This will build the Perl interpreter for NetWare as perl.nlm. This is copied under the Release folder if you are doing a release build, else will be copied under Debug folder for debug builds. Extensions The make process also creates the Perl extensions as <Extension.nlm> INSTALL
To install NetWare Perl onto a NetWare server, first map the Sys volume of a NetWare server to i:. This is because the makefile by default sets the drive letter to i:. Type nmake nwinstall from NetWare folder on a WinNT command prompt. This will copy the binaries and module files onto the NetWare server under sys:Perl folder. The Perl interpreter, perl.nlm, is copied under sys:perlsystem folder. Copy this to sys:system folder. Example: At the command prompt Type "nmake nwinstall". This will install NetWare Perl on the NetWare Server. Similarly, if you type "nmake install", this will cause the binaries to be installed on the local machine. (Typically under the c:perl folder) BUILD NEW EXTENSIONS
To build extensions other than standard extensions, NetWare Perl has to be installed on Windows along with Windows Perl. The Perl for Windows can be either downloaded from the CPAN site and built using the sources, or the binaries can be directly downloaded from the ActiveState site. Installation can be done by invoking nmake install from the NetWare folder on a WinNT command prompt after building NetWare Perl by following steps given above. This will copy all the *.pm files and other required files. Documentation files are not copied. Thus one must first install Windows Perl, Then install NetWare Perl. Once this is done, do the following to build any extension: o Change to the extension directory where its source files are present. o Run the following command at the command prompt: perl -II<path to NetWare lib dir> -II<path to lib> Makefile.pl Example: perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:perl5.6.1lib MakeFile.pl or perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:perl5.8.0lib MakeFile.pl o nmake o nmake install Install will copy the files into the Windows machine where NetWare Perl is installed and these files may have to be copied to the NetWare server manually. Alternatively, pass INSTALLSITELIB=i:perllib as an input to makefile.pl above. Here i: is the mapped drive to the sys: volume of the server where Perl on NetWare is installed. Now typing nmake install, will copy the files onto the NetWare server. Example: You can execute the following on the command prompt. perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:perl5.6.1lib MakeFile.pl INSTALLSITELIB=i:perllib or perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:perl5.8.0lib MakeFile.pl INSTALLSITELIB=i:perllib o Note: Some modules downloaded from CPAN may require NetWare related API in order to build on NetWare. Other modules may however build smoothly with or without minor changes depending on the type of module. ACKNOWLEDGEMENTS
The makefile for Win32 is used as a reference to create the makefile for NetWare. Also, the make process for NetWare port uses miniperl.exe to run scripts during the make and installation process. AUTHORS
Anantha Kesari H Y (hyanantha@novell.com) Aditya C (caditya@novell.com) DATE
o Created - 18 Jan 2001 o Modified - 25 June 2001 o Modified - 13 July 2001 o Modified - 28 May 2002 perl v5.18.2 2014-01-06 PERLNETWARE(1)