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:

   *   USE_MULTI, USE_ITHREADS & USE_IMP_SYS defined

   *   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:\perl\system 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:

   *   Change to the extension directory where its source files are
       present.

   *   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:\perl\5.6.1\lib MakeFile.pl

       or

           perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread           \
                                       -Ic:\perl\5.8.0\lib MakeFile.pl

   *   nmake

   *   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:\perl\lib 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:\perl\5.6.1\lib MakeFile.pl
         INSTALLSITELIB=i:\perl\lib

       or

         perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread             \
                                       -Ic:\perl\5.8.0\lib MakeFile.pl
         INSTALLSITELIB=i:\perl\lib

   *   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

   *   Created - 18 Jan 2001

   *   Modified - 25 June 2001

   *   Modified - 13 July 2001

   *   Modified - 28 May 2002


More Linux Commands

manpages/keyctl_read.3.html
keyctl_read(3) - Read a key (Library - Linux man page)......
keyctl_read() reads the payload of a key if the key type supports it. The caller must have read permission on a key to be able to read it. buffer and buflen spe

manpages/perl5120delta.1.html
perl5120delta(1) - what is new for perl v5.12.0 (Man Page)
This document describes differences between the 5.10.0 release and the 5.12.0 release. Many of the bug fixes in 5.12.0 are already included in the 5.10.1 mainte

manpages/ksh93.1ast.html
ksh93(1ast) KornShell, a standard restricted command and pro
Ksh is a command and programming language that executes commands read from a terminal or a file. Rksh is a restricted version of the command interpreter ksh; it

manpages/symcryptrun.1.html
symcryptrun(1) - Call a simple symmetric encryption tool....
Sometimes simple encryption tools are already in use for a long time and there might be a desire to integrate them into the GnuPG framework. The protocols and e

manpages/_traceattr2.3ncurses.html
_traceattr2(3ncurses) - curses debugging routines (ManPage)
The trace routines are used for debugging the ncurses libraries, as well as applications which use the ncurses libraries. These functions are normally available

manpages/uuid_unparse.3.html
uuid_unparse(3) - convert an UUID from binary representation
The uuid_unparse function converts the supplied UUID uu from the binary representation into a 36-byte string (plus tailing \0) of the form 1b4e28ba-2fa1-11d2-88

manpages/gnutls_perror.3.html
gnutls_perror(3) - API function (Library - Linux man page)
This function is like perror(). The only difference is that it accepts an error number returned by a gnutls function. REPORTING BUGS Report bugs to &lt;bug-gnutls@

manpages/r128.4.html
r128(4) - ATI Rage 128 video driver - Linux manual page.....
r128 is an Xorg driver for ATI Rage 128 based video cards. It contains full support for 8, 15, 16 and 24 bit pixel depths, hardware acceleration of drawing prim

manpages/Tcl_NewStringObj.3.html
Tcl_NewStringObj(3) - manipulate Tcl objects as strings.....
The procedures described in this manual entry allow Tcl objects to be manipulated as string values. They use the internal representation of the object to store

manpages/XkbComputeSectionBounds.3.html
XkbComputeSectionBounds(3) - Update the bounding box of a se
If you add or delete a row to or from a section, or if you change the geometry of any of the rows in that section, you may need to update the bounding box for t

manpages/isinf.3.html
isinf(3) - floating-point classification macros (Man Page)
Floating point numbers can have special values, such as infinite or NaN. With the macro fpclassify(x) you can find out what type x is. The macro takes any float

manpages/Tcl_GetEncodingFromObj.3.html
Tcl_GetEncodingFromObj(3) - procedures for creating and usin
Tcl_GetEncoding finds an encoding given its name. The name may refer to a built-in Tcl encoding, a user-defined encoding registered by calling Tcl_CreateEncodin





We can't live, work or learn in freedom unless the software we use is free.