| 1 | If you read this file _as_is_, just ignore the equal signs on the left. |
| 2 | This file is written in the POD format (see [.POD]PERLPOD.POD;1) which is |
| 3 | specially designed to be readable as is. |
| 4 | |
| 5 | =head1 NAME |
| 6 | |
| 7 | README.vms - Configuring, building, testing, and installing perl on VMS |
| 8 | |
| 9 | =head1 SYNOPSIS |
| 10 | |
| 11 | To configure, build, test, and install perl on VMS: |
| 12 | |
| 13 | @ Configure |
| 14 | mms |
| 15 | mms test |
| 16 | mms install |
| 17 | |
| 18 | mmk may be used in place of mms in the last three steps. |
| 19 | |
| 20 | =head1 DESCRIPTION |
| 21 | |
| 22 | =head2 Important safety tip |
| 23 | |
| 24 | The build and install procedures have changed significantly from the 5.004 |
| 25 | releases! Make sure you read the "Configuring the Perl Build", "Building |
| 26 | Perl", and "Installing Perl" sections of this document before you build or |
| 27 | install. |
| 28 | |
| 29 | Also note that, as of Perl version 5.005 and later, an ANSI C compliant |
| 30 | compiler is required to build Perl. VAX C is *not* ANSI compliant, as it |
| 31 | died a natural death some time before the standard was set. Therefore |
| 32 | VAX C will not compile Perl 5.005 or later. We are sorry about that. |
| 33 | |
| 34 | If you are stuck without DEC C (the VAX C license should be good for DEC C, |
| 35 | but the media charges might prohibit an upgrade), consider getting Gnu C |
| 36 | instead. |
| 37 | |
| 38 | |
| 39 | =head2 Introduction to Perl on VMS |
| 40 | |
| 41 | The VMS port of Perl is as functionally complete as any other Perl port |
| 42 | (and as complete as the ports on some Unix systems). The Perl binaries |
| 43 | provide all the Perl system calls that are either available under VMS or |
| 44 | reasonably emulated. There are some incompatibilities in process handling |
| 45 | (e.g. the fork/exec model for creating subprocesses doesn't do what you |
| 46 | might expect under Unix), mainly because VMS and Unix handle processes and |
| 47 | sub-processes very differently. |
| 48 | |
| 49 | There are still some unimplemented system functions, and of course we |
| 50 | could use modules implementing useful VMS system services, so if you'd like |
| 51 | to lend a hand we'd love to have you. Join the Perl Porting Team Now! |
| 52 | |
| 53 | The current sources and build procedures have been tested on a VAX using |
| 54 | DEC C, and on an AXP using DEC C. If you run into problems with |
| 55 | other compilers, please let us know. (Note: DEC C was renamed to Compaq C |
| 56 | around version 6.2). |
| 57 | |
| 58 | There are issues with various versions of DEC C, so if you're not running a |
| 59 | relatively modern version, check the "DEC C issues" section later on in this |
| 60 | document. |
| 61 | |
| 62 | =head2 Other required software for Compiling Perl on VMS |
| 63 | |
| 64 | In addition to VMS and DCL you will need two things: |
| 65 | |
| 66 | =over 4 |
| 67 | |
| 68 | =item 1 A C compiler. |
| 69 | |
| 70 | DEC (now Compaq) C or gcc for VMS (AXP or VAX). |
| 71 | |
| 72 | =item 2 A make tool. |
| 73 | |
| 74 | DEC's MMS (v2.6 or later), or MadGoat's free MMS |
| 75 | analog MMK (available from ftp.madgoat.com/madgoat) both work |
| 76 | just fine. Gnu Make might work, but it's been so long since |
| 77 | anyone's tested it that we're not sure. MMK is free though, so |
| 78 | go ahead and use that. |
| 79 | |
| 80 | =back |
| 81 | |
| 82 | =head2 Additional software that is optional for Perl on VMS |
| 83 | |
| 84 | You may also want to have on hand: |
| 85 | |
| 86 | =over 4 |
| 87 | |
| 88 | =item 1 GUNZIP/GZIP.EXE for VMS |
| 89 | |
| 90 | A de-compressor for *.gz and *.tgz files available from a number |
| 91 | of web/ftp sites and is distributed on the OpenVMS Freeware CD-ROM |
| 92 | from Compaq. |
| 93 | |
| 94 | http://www.fsf.org/order/ftp.html |
| 95 | http://www.openvms.compaq.com/freeware/GZIP/ |
| 96 | ftp://ftp.compaq.com/pub/VMS/ |
| 97 | http://www.crinoid.com/utils/ |
| 98 | |
| 99 | =item 2 VMS TAR |
| 100 | |
| 101 | For reading and writing unix tape archives (*.tar files). Vmstar is also |
| 102 | available from a number of web/ftp sites and is distributed on the OpenVMS |
| 103 | Freeware CD-ROM from Compaq. |
| 104 | |
| 105 | ftp://ftp.lp.se/vms/ |
| 106 | http://www.openvms.compaq.com/freeware/VMSTAR/ |
| 107 | ftp://ftp.compaq.com/pub/VMS/ |
| 108 | |
| 109 | =item 3 UNZIP.EXE for VMS |
| 110 | |
| 111 | A combination decompressor and archive reader/writer for *.zip files. |
| 112 | Unzip is available from a number of web/ftp sites. |
| 113 | |
| 114 | http://www.cdrom.com/pub/infozip/UnZip.html |
| 115 | http://www.openvms.compaq.com/freeware/INFO-ZIP/ |
| 116 | ftp://ftp.compaq.com/pub/VMS/ |
| 117 | ftp://ftp.openvms.compaq.com/ |
| 118 | ftp://ftp.madgoat.com/madgoat/ |
| 119 | ftp://ftp.wku.edu/vms/ |
| 120 | |
| 121 | =item 4 MOST |
| 122 | |
| 123 | Most is an optional pager that is convenient to use with perldoc (unlike |
| 124 | TYPE/PAGE, MOST can go forward and backwards in a document and supports |
| 125 | regular expression searching). Most builds with the slang |
| 126 | library on VMS. Most and slang are available from: |
| 127 | |
| 128 | ftp://space.mit.edu/pub/davis/ |
| 129 | ftp://ftp.wku.edu/vms/narnia/most.zip |
| 130 | |
| 131 | =item 5 GNU PATCH and DIFFUTILS for VMS |
| 132 | |
| 133 | Patches to Perl are usually distributed as GNU unified or contextual diffs. |
| 134 | Such patches are created by the GNU diff program (part of the diffutils |
| 135 | distribution) and applied with GNU patch. VMS ports of these utilities are |
| 136 | available here: |
| 137 | |
| 138 | http://www.crinoid.com/utils/ |
| 139 | |
| 140 | =back |
| 141 | |
| 142 | Please note that UNZIP and GUNZIP are not the same thing (they work with |
| 143 | different formats). Many of the useful files from CPAN (the Comprehensive |
| 144 | Perl Archive Network) are in *.tar.gz or *.tgz format (this includes copies |
| 145 | of the source code for perl as well as modules and scripts that you may |
| 146 | wish to add later) hence you probably want to have GUNZIP.EXE and |
| 147 | VMSTAR.EXE on your VMS machine. |
| 148 | |
| 149 | If you want to include socket support, you'll need a TCP/IP stack and either |
| 150 | DEC C, or socket libraries. See the "Socket Support (optional)" topic |
| 151 | for more details. |
| 152 | |
| 153 | =head1 Configuring the Perl build |
| 154 | |
| 155 | To configure perl (a necessary first step), issue the command |
| 156 | |
| 157 | @ Configure |
| 158 | |
| 159 | from the top of an unpacked perl source directory. You will be asked a |
| 160 | series of questions, and the answers to them (along with the capabilities |
| 161 | of your C compiler and network stack) will determine how perl is custom |
| 162 | built for your machine. |
| 163 | |
| 164 | If you have multiple C compilers installed, you'll have your choice of |
| 165 | which one to use. Various older versions of DEC C had some caveats, so if |
| 166 | you're using a version older than 5.2, check the "DEC C Issues" section. |
| 167 | |
| 168 | If you have any symbols or logical names in your environment that may |
| 169 | interfere with the build or regression testing of perl then configure.com |
| 170 | will try to warn you about them. If a logical name is causing |
| 171 | you trouble but is in an LNM table that you do not have write access to |
| 172 | then try defining your own to a harmless equivalence string in a table |
| 173 | such that it is resolved before the other (e.g. if TMP is defined in the |
| 174 | SYSTEM table then try DEFINE TMP "NL:" or somesuch in your process table) |
| 175 | otherwise simply deassign the dangerous logical names. The potentially |
| 176 | troublesome logicals and symbols are: |
| 177 | |
| 178 | TMP "LOGICAL" |
| 179 | LIB "LOGICAL" |
| 180 | T "LOGICAL" |
| 181 | FOO "LOGICAL" |
| 182 | EXT "LOGICAL" |
| 183 | SOME_LOGICAL_NAME_NOT_LIKELY "LOGICAL" |
| 184 | DOWN_LOGICAL_NAME_NOT_LIKELY "LOGICAL" |
| 185 | TEST "SYMBOL" |
| 186 | |
| 187 | As a handy shortcut, the command: |
| 188 | |
| 189 | @ Configure "-des" |
| 190 | |
| 191 | (note the quotation marks and case) will choose reasonable defaults |
| 192 | automatically (it takes DEC C over Gnu C, DEC C sockets over SOCKETSHR |
| 193 | sockets, and either over no sockets). Some options can be given |
| 194 | explicitly on the command line; the following example specifies a |
| 195 | non-default location for where Perl will be installed: |
| 196 | |
| 197 | @ Configure "-d" "-Dprefix=dka100:[utils.perl5.]" |
| 198 | |
| 199 | Note that the installation location would be by default where you unpacked |
| 200 | the source with a "ROOT." appended. For example if you unpacked the perl |
| 201 | source into: |
| 202 | |
| 203 | DKA200:[PERL-5_10_2...] |
| 204 | |
| 205 | Then the PERL_SETUP.COM that gets written out by Configure.com will |
| 206 | try to DEFINE your installation PERL_ROOT to be: |
| 207 | |
| 208 | DKA200:[PERL-5_10_2ROOT.] |
| 209 | |
| 210 | More help with configure.com is available from: |
| 211 | |
| 212 | @ Configure "-h" |
| 213 | |
| 214 | See the "Changing compile-time options (optional)" section below to learn |
| 215 | even more details about how to influence the outcome of the important |
| 216 | configuration step. If you find yourself reconfiguring and rebuilding |
| 217 | then be sure to also follow the advice in the "Cleaning up and starting |
| 218 | fresh (optional)" and the checklist of items in the "CAVEATS" sections |
| 219 | below. |
| 220 | |
| 221 | =head2 Changing compile-time options (optional) for Perl on VMS |
| 222 | |
| 223 | Most of the user definable features of Perl are enabled or disabled in |
| 224 | [.VMS]CONFIG.VMS. There is code in there to Do The Right Thing, but that |
| 225 | may end up being the wrong thing for you. Make sure you understand what |
| 226 | you are doing since inappropriate changes to CONFIG.VMS can render perl |
| 227 | unbuildable. |
| 228 | |
| 229 | Odds are that there's nothing here to change, unless you're on a version of |
| 230 | VMS later than 6.2 and DEC C later than 5.6. Even if you are, the correct |
| 231 | values will still be chosen, most likely. Poking around here should be |
| 232 | unnecessary. |
| 233 | |
| 234 | The one exception is the various *DIR install locations. Changing those |
| 235 | requires changes in genconfig.pl as well. Be really careful if you need to |
| 236 | change these, as they can cause some fairly subtle problems. |
| 237 | |
| 238 | =head2 Socket Support (optional) for Perl on VMS |
| 239 | |
| 240 | Perl includes a number of functions for IP sockets, which are available if |
| 241 | you choose to compile Perl with socket support. Since IP networking is an |
| 242 | optional addition to VMS, there are several different IP stacks available. |
| 243 | How well integrated they are into the system depends on the stack, your |
| 244 | version of VMS, and the version of your C compiler. |
| 245 | |
| 246 | The most portable solution uses the SOCKETSHR library. In combination with |
| 247 | either UCX or NetLib, this supports all the major TCP stacks (Multinet, |
| 248 | Pathways, TCPWare, UCX, and CMU) on all versions of VMS Perl runs on, with |
| 249 | all the compilers on both VAX and Alpha. The socket interface is also |
| 250 | consistent across versions of VMS and C compilers. It has a problem with |
| 251 | UDP sockets when used with Multinet, though, so you should be aware of |
| 252 | that. |
| 253 | |
| 254 | The other solution available is to use the socket routines built into DEC |
| 255 | C. Which routines are available depend on the version of VMS you're |
| 256 | running, and require proper UCX emulation by your TCP/IP vendor. |
| 257 | Relatively current versions of Multinet, TCPWare, Pathway, and UCX all |
| 258 | provide the required libraries--check your manuals or release notes to see |
| 259 | if your version is new enough. |
| 260 | |
| 261 | =head1 Building Perl |
| 262 | |
| 263 | The configuration script will print out, at the very end, the MMS or MMK |
| 264 | command you need to compile perl. Issue it (exactly as printed) to start |
| 265 | the build. |
| 266 | |
| 267 | Once you issue your MMS or MMK command, sit back and wait. Perl should |
| 268 | compile and link without a problem. If a problem does occur check the |
| 269 | "CAVEATS" section of this document. If that does not help send some |
| 270 | mail to the VMSPERL mailing list. Instructions are in the "Mailing Lists" |
| 271 | section of this document. |
| 272 | |
| 273 | =head1 Testing Perl |
| 274 | |
| 275 | Once Perl has built cleanly you need to test it to make sure things work. |
| 276 | This step is very important since there are always things that can go wrong |
| 277 | somehow and yield a dysfunctional Perl for you. |
| 278 | |
| 279 | Testing is very easy, though, as there's a full test suite in the perl |
| 280 | distribution. To run the tests, enter the *exact* MMS line you used to |
| 281 | compile Perl and add the word "test" to the end, like this: |
| 282 | |
| 283 | If the compile command was: |
| 284 | |
| 285 | MMS |
| 286 | |
| 287 | then the test command ought to be: |
| 288 | |
| 289 | MMS test |
| 290 | |
| 291 | MMS (or MMK) will run all the tests. This may take some time, as there are |
| 292 | a lot of tests. If any tests fail, there will be a note made on-screen. |
| 293 | At the end of all the tests, a summary of the tests, the number passed and |
| 294 | failed, and the time taken will be displayed. |
| 295 | |
| 296 | If any tests fail, it means something is wrong with Perl. If the test suite |
| 297 | hangs (some tests can take upwards of two or three minutes, or more if |
| 298 | you're on an especially slow machine, depending on your machine speed, so |
| 299 | don't be hasty), then the test *after* the last one displayed failed. Don't |
| 300 | install Perl unless you're confident that you're OK. Regardless of how |
| 301 | confident you are, make a bug report to the VMSPerl mailing list. |
| 302 | |
| 303 | If one or more tests fail, you can get more information on the failure by |
| 304 | issuing this command sequence: |
| 305 | |
| 306 | @ [.VMS]TEST .typ "" "-v" [.subdir]test.T |
| 307 | |
| 308 | where ".typ" is the file type of the Perl images you just built (if you |
| 309 | didn't do anything special, use .EXE), and "[.subdir]test.T" is the test |
| 310 | that failed. For example, with a normal Perl build, if the test indicated |
| 311 | that [.op]time failed, then you'd do this: |
| 312 | |
| 313 | @ [.VMS]TEST .EXE "" "-v" [.OP]TIME.T |
| 314 | |
| 315 | When you send in a bug report for failed tests, please include the output |
| 316 | from this command, which is run from the main source directory: |
| 317 | |
| 318 | MCR []MINIPERL "-V" |
| 319 | |
| 320 | Note that -"V" really is a capital V in double quotes. This will dump out a |
| 321 | couple of screens worth of configuration information, and can help us |
| 322 | diagnose the problem. If (and only if) that did not work then try enclosing |
| 323 | the output of: |
| 324 | |
| 325 | MMS printconfig |
| 326 | |
| 327 | If (and only if) that did not work then try enclosing the output of: |
| 328 | |
| 329 | @ [.vms]myconfig |
| 330 | |
| 331 | You may also be asked to provide your C compiler version ("CC/VERSION NL:" |
| 332 | with DEC C, "gcc --version" with GNU CC). To obtain the version of MMS or |
| 333 | MMK you are running try "MMS/ident" or "MMK /ident". The GNU make version |
| 334 | can be identified with "make --version". |
| 335 | |
| 336 | =head2 Cleaning up and starting fresh (optional) installing Perl on VMS |
| 337 | |
| 338 | If you need to recompile from scratch, you have to make sure you clean up |
| 339 | first. There is a procedure to do it--enter the *exact* MMS line you used |
| 340 | to compile and add "realclean" at the end, like this: |
| 341 | |
| 342 | if the compile command was: |
| 343 | |
| 344 | MMS |
| 345 | |
| 346 | then the cleanup command ought to be: |
| 347 | |
| 348 | MMS realclean |
| 349 | |
| 350 | If you do not do this things may behave erratically during the subsequent |
| 351 | rebuild attempt. They might not, too, so it is best to be sure and do it. |
| 352 | |
| 353 | =head1 Installing Perl |
| 354 | |
| 355 | There are several steps you need to take to get Perl installed and |
| 356 | running. |
| 357 | |
| 358 | =over 4 |
| 359 | |
| 360 | =item 1 |
| 361 | |
| 362 | Check your default file protections with |
| 363 | |
| 364 | SHOW PROTECTION /DEFAULT |
| 365 | |
| 366 | and adjust if necessary with SET PROTECTION=(code)/DEFAULT. |
| 367 | |
| 368 | =item 2 |
| 369 | |
| 370 | Decide where you want Perl to be installed (unless you have already done so |
| 371 | by using the "prefix" configuration parameter -- see the example in the |
| 372 | "Configuring the Perl build" section). |
| 373 | |
| 374 | The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM will help you |
| 375 | with the definition of the PERL_ROOT and PERLSHR logical names and the PERL |
| 376 | foreign command symbol. Take a look at PERL_SETUP.COM and modify it if you |
| 377 | want to. The installation process will execute PERL_SETUP.COM and copy |
| 378 | files to the directory tree pointed to by the PERL_ROOT logical name defined |
| 379 | there, so make sure that you have write access to the parent directory of |
| 380 | what will become the root of your Perl installation. |
| 381 | |
| 382 | =item 3 |
| 383 | |
| 384 | Run the install script via: |
| 385 | |
| 386 | MMS install |
| 387 | |
| 388 | or |
| 389 | |
| 390 | MMK install |
| 391 | |
| 392 | If for some reason it complains about target INSTALL being up to date, |
| 393 | throw a /FORCE switch on the MMS or MMK command. |
| 394 | |
| 395 | =back |
| 396 | |
| 397 | Copy PERL_SETUP.COM to a place accessible to your perl users. |
| 398 | |
| 399 | For example: |
| 400 | |
| 401 | COPY PERL_SETUP.COM SYS$LIBRARY: |
| 402 | |
| 403 | If you want to have everyone on the system have access to perl |
| 404 | then add a line that reads |
| 405 | |
| 406 | $ @sys$library:perl_setup |
| 407 | |
| 408 | to SYS$MANAGER:SYLOGIN.COM. |
| 409 | |
| 410 | Two alternatives to the foreign symbol would be to install PERL into |
| 411 | DCLTABLES.EXE (Check out the section "Installing Perl into DCLTABLES |
| 412 | (optional)" for more information), or put the image in a |
| 413 | directory that's in your DCL$PATH (if you're using VMS V6.2 or higher). |
| 414 | |
| 415 | An alternative to having PERL_SETUP.COM define the PERLSHR logical name |
| 416 | is to simply copy it into the system shareable library directory with: |
| 417 | |
| 418 | copy perl_root:[000000]perlshr.exe sys$share: |
| 419 | |
| 420 | See also the "INSTALLing images (optional)" section. |
| 421 | |
| 422 | =head2 Installing Perl into DCLTABLES (optional) on VMS |
| 423 | |
| 424 | Execute the following command file to define PERL as a DCL command. |
| 425 | You'll need CMKRNL privilege to install the new dcltables.exe. |
| 426 | |
| 427 | $ create perl.cld |
| 428 | ! |
| 429 | ! modify to reflect location of your perl.exe |
| 430 | ! |
| 431 | define verb perl |
| 432 | image perl_root:[000000]perl.exe |
| 433 | cliflags (foreign) |
| 434 | $! |
| 435 | $ set command perl /table=sys$common:[syslib]dcltables.exe - |
| 436 | /output=sys$common:[syslib]dcltables.exe |
| 437 | $ install replace sys$common:[syslib]dcltables.exe |
| 438 | $ exit |
| 439 | |
| 440 | =head2 INSTALLing Perl images (optional) on VMS |
| 441 | |
| 442 | On systems that are using perl quite a bit, and particularly those with |
| 443 | minimal RAM, you can boost the performance of perl by INSTALLing it as |
| 444 | a known image. PERLSHR.EXE is typically larger than 2500 blocks |
| 445 | and that is a reasonably large amount of IO to load each time perl is |
| 446 | invoked. |
| 447 | |
| 448 | INSTALL ADD PERLSHR/SHARE |
| 449 | INSTALL ADD PERL/HEADER |
| 450 | |
| 451 | should be enough for PERLSHR.EXE (/share implies /header and /open), |
| 452 | while /HEADER should do for PERL.EXE (perl.exe is not a shared image). |
| 453 | |
| 454 | If your code 'use's modules, check to see if there is a shareable image for |
| 455 | them, too. In the base perl build, POSIX, IO, Fcntl, Opcode, SDBM_File, |
| 456 | DCLsym, and Stdio all have shared images that can be installed /SHARE. |
| 457 | |
| 458 | How much of a win depends on your memory situation, but if you are firing |
| 459 | off perl with any regularity (like more than once every 20 seconds or so) |
| 460 | it is probably beneficial to INSTALL at least portions of perl. |
| 461 | |
| 462 | While there is code in perl to remove privileges as it runs you are advised |
| 463 | to NOT INSTALL PERL.EXE with PRIVs! |
| 464 | |
| 465 | =head2 Running h2ph to create perl header files (optional) on VMS |
| 466 | |
| 467 | If using DEC C or Compaq C ensure that you have extracted loose versions |
| 468 | of your compiler's header or *.H files. Be sure to check the contents of: |
| 469 | |
| 470 | SYS$LIBRARY:DECC$RTLDEF.TLB |
| 471 | SYS$LIBRARY:SYS$LIB_C.TLB |
| 472 | SYS$LIBRARY:SYS$STARLET_C.TLB |
| 473 | |
| 474 | etcetera. |
| 475 | |
| 476 | If using GNU cc then also check your GNU_CC:[000000...] tree for the locations |
| 477 | of the GNU cc headers. |
| 478 | |
| 479 | =head1 Reporting Bugs |
| 480 | |
| 481 | If you come across what you think might be a bug in Perl, please report |
| 482 | it. There's a script in PERL_ROOT:[UTILS], perlbug, that walks you through |
| 483 | the process of creating a bug report. This script includes details of your |
| 484 | installation, and is very handy. Completed bug reports should go to |
| 485 | perlbug@perl.com. |
| 486 | |
| 487 | =head1 CAVEATS |
| 488 | |
| 489 | Probably the single biggest gotcha in compiling Perl is giving the wrong |
| 490 | switches to MMS/MMK when you build. Use *exactly* what the configure.com |
| 491 | script prints! |
| 492 | |
| 493 | The next big gotcha is directory depth. Perl can create directories four, |
| 494 | five, or even six levels deep during the build, so you don't have to be |
| 495 | too deep to start to hit the RMS 8 level limit (for ODS 2 volumes which were |
| 496 | common on versions of VMS prior to V7.2 and even with V7.2 on the VAX). |
| 497 | It is best to do: |
| 498 | |
| 499 | DEFINE/TRANS=(CONC,TERM) PERLSRC "disk:[dir.dir.dir.perldir.]" |
| 500 | SET DEFAULT PERLSRC:[000000] |
| 501 | |
| 502 | before building in cases where you have to unpack the distribution so deep |
| 503 | (note the trailing period in the definition of PERLSRC). Perl modules |
| 504 | from CPAN can be just as bad (or worse), so watch out for them, too. Perl's |
| 505 | configuration script will warn if it thinks you are too deep (at least on |
| 506 | a VAX or on Alpha versions of VMS prior to 7.2). But MakeMaker will not |
| 507 | warn you if you start out building a module too deep in a directory. |
| 508 | |
| 509 | Be sure that the process that you use to build perl has a PGFLQ greater |
| 510 | than 100000. Be sure to have a correct local time zone to UTC offset |
| 511 | defined (in seconds) in the logical name SYS$TIMEZONE_DIFFERENTIAL before |
| 512 | running the regression test suite. The SYS$MANAGER:UTC$CONFIGURE_TDF.COM |
| 513 | procedure will help you set that logical for your system but may require |
| 514 | system privileges. For example, a location 5 hours west of UTC (such as |
| 515 | the US East coast while not on daylight savings time) would have: |
| 516 | |
| 517 | DEFINE SYS$TIMEZONE_DIFFERENTIAL "-18000" |
| 518 | |
| 519 | A final thing that causes trouble is leftover pieces from a failed |
| 520 | build. If things go wrong make sure you do a "(MMK|MMS|make) realclean" |
| 521 | before you rebuild. |
| 522 | |
| 523 | =head2 DEC C issues with Perl on VMS |
| 524 | |
| 525 | Note to DEC C users: Some early versions (pre-5.2, some pre-4. If you're DEC |
| 526 | C 5.x or higher, with current patches if any, you're fine) of the DECCRTL |
| 527 | contained a few bugs which affect Perl performance: |
| 528 | |
| 529 | =over 4 |
| 530 | |
| 531 | =item - pipes |
| 532 | |
| 533 | Newlines are lost on I/O through pipes, causing lines to run together. |
| 534 | This shows up as RMS RTB errors when reading from a pipe. You can |
| 535 | work around this by having one process write data to a file, and |
| 536 | then having the other read the file, instead of the pipe. This is |
| 537 | fixed in version 4 of DEC C. |
| 538 | |
| 539 | =item - modf() |
| 540 | |
| 541 | The modf() routine returns a non-integral value for some values above |
| 542 | INT_MAX; the Perl "int" operator will return a non-integral value in |
| 543 | these cases. This is fixed in version 4 of DEC C. |
| 544 | |
| 545 | =item - ALPACRT ECO |
| 546 | |
| 547 | On the AXP, if SYSNAM privilege is enabled, the CRTL chdir() routine |
| 548 | changes the process default device and directory permanently, even |
| 549 | though the call specified that the change should not persist after |
| 550 | Perl exited. This is fixed by DEC CSC patch ALPACRT04_061 or later. |
| 551 | See also: |
| 552 | |
| 553 | http://ftp.service.compaq.com/patches/.new/openvms.html |
| 554 | |
| 555 | =back |
| 556 | |
| 557 | Please note that in later versions "DEC C" may also be known as |
| 558 | "Compaq C". |
| 559 | |
| 560 | =head2 GNU issues with Perl on VMS |
| 561 | |
| 562 | It has been a while since the GNU utilities such as GCC or GNU make |
| 563 | were used to build perl on VMS. Hence they may require a great deal |
| 564 | of source code modification to work again. |
| 565 | |
| 566 | http://slacvx.slac.stanford.edu/HELP/GCC |
| 567 | http://www.progis.de/ |
| 568 | http://vms.gnu.org/ |
| 569 | http://www.lp.se/products/gnu.html |
| 570 | |
| 571 | =head1 Mailing Lists |
| 572 | |
| 573 | There are several mailing lists available to the Perl porter. For VMS |
| 574 | specific issues (including both Perl questions and installation problems) |
| 575 | there is the VMSPERL mailing list. It is usually a low-volume (10-12 |
| 576 | messages a week) mailing list. |
| 577 | |
| 578 | To subscribe, send a mail message to VMSPERL-SUBSCRIBE@PERL.ORG. The VMSPERL |
| 579 | mailing list address is VMSPERL@PERL.ORG. Any mail sent there gets echoed |
| 580 | to all subscribers of the list. There is a searchable archive of the list |
| 581 | on the web at: |
| 582 | |
| 583 | http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/ |
| 584 | |
| 585 | To unsubscribe from VMSPERL send a message to VMSPERL-UNSUBSCRIBE@PERL.ORG. |
| 586 | Be sure to do so from the subscribed account that you are canceling. |
| 587 | |
| 588 | =head2 Web sites for Perl on VMS |
| 589 | |
| 590 | Vmsperl pages on the web include: |
| 591 | |
| 592 | http://www.sidhe.org/vmsperl/index.html |
| 593 | http://www.crinoid.com/ |
| 594 | http://duphy4.physics.drexel.edu/pub/cgi_info.htmlx |
| 595 | http://www.cpan.org/modules/by-module/VMS/ |
| 596 | http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/ |
| 597 | http://nucwww.chem.sunysb.edu/htbin/software_list.cgi |
| 598 | http://www.best.com/~pvhp/vms/ |
| 599 | http://bkfug.kfunigraz.ac.at/~binder/perl.html |
| 600 | http://lists.perl.org/showlist.cgi?name=vmsperl |
| 601 | http://archive.develooper.com/vmsperl@perl.org/ |
| 602 | |
| 603 | =head1 SEE ALSO |
| 604 | |
| 605 | Perl information for users and programmers about the port of perl to VMS is |
| 606 | available from the [.VMS]PERLVMS.POD file that gets installed as L<perlvms>. |
| 607 | For administrators the perlvms document also includes a detailed discussion |
| 608 | of extending vmsperl with CPAN modules after Perl has been installed. |
| 609 | |
| 610 | =head1 AUTHORS |
| 611 | |
| 612 | Revised 5-April-2001 by Craig Berry craigberry@mac.com. |
| 613 | Revised 25-February-2000 by Peter Prymmer pvhp@best.com. |
| 614 | Revised 27-October-1999 by Craig Berry craigberry@mac.com. |
| 615 | Revised 01-March-1999 by Dan Sugalski dan@sidhe.org. |
| 616 | Originally by Charles Bailey bailey@newman.upenn.edu. |
| 617 | |
| 618 | =head1 ACKNOWLEDGEMENTS |
| 619 | |
| 620 | A real big thanks needs to go to Charles Bailey |
| 621 | bailey@newman.upenn.edu, who is ultimately responsible for Perl 5.004 |
| 622 | running on VMS. Without him, nothing the rest of us have done would be at |
| 623 | all important. |
| 624 | |
| 625 | There are, of course, far too many people involved in the porting and testing |
| 626 | of Perl to mention everyone who deserves it, so please forgive us if we've |
| 627 | missed someone. That said, special thanks are due to the following: |
| 628 | |
| 629 | Tim Adye T.J.Adye@rl.ac.uk |
| 630 | for the VMS emulations of getpw*() |
| 631 | David Denholm denholm@conmat.phys.soton.ac.uk |
| 632 | for extensive testing and provision of pipe and SocketShr code, |
| 633 | Mark Pizzolato mark@infocomm.com |
| 634 | for the getredirection() code |
| 635 | Rich Salz rsalz@bbn.com |
| 636 | for readdir() and related routines |
| 637 | Peter Prymmer pvhp@best.com |
| 638 | for extensive testing, as well as development work on |
| 639 | configuration and documentation for VMS Perl, |
| 640 | Dan Sugalski dan@sidhe.org |
| 641 | for extensive contributions to recent version support, |
| 642 | development of VMS-specific extensions, and dissemination |
| 643 | of information about VMS Perl, |
| 644 | the Stanford Synchrotron Radiation Laboratory and the |
| 645 | Laboratory of Nuclear Studies at Cornell University for |
| 646 | the opportunity to test and develop for the AXP, |
| 647 | John Hasstedt John.Hasstedt@sunysb.edu |
| 648 | for VAX VMS V7.2 support |
| 649 | |
| 650 | and to the entire VMSperl group for useful advice and suggestions. In |
| 651 | addition the perl5-porters deserve credit for their creativity and |
| 652 | willingness to work with the VMS newcomers. Finally, the greatest debt of |
| 653 | gratitude is due to Larry Wall larry@wall.org, for having the ideas which |
| 654 | have made our sleepless nights possible. |
| 655 | |
| 656 | Thanks, |
| 657 | The VMSperl group |
| 658 | |
| 659 | =cut |
| 660 | |