Yes thanks! that did the trick - I was running the configure interactively.
-Jim >>> "Craig A. Berry" <[EMAIL PROTECTED]> 05/13/02 08:03PM >>> At 4:10 PM -0700 5/13/02, Jim Rouff wrote: >Hi, > >I downloaded Craig Berry's 5.6.1 perlbuild.zip on 05/06/2002 from >www.sidhe.org. > >Compaq C V6.4-008-46B45 on a GS80 cluster, OpenVMS AXP V7.3 > >I have another version of perl already running so I defined > >"PERLKIT" = "$1$DGA123:[PERL_TEST.PERLBUILD.]" > "PERLSHR" = "PERL_ROOT:[000000]PERLSHR.EXE" > "PERL_ROOT" = "$1$DGA123:[PERL_TEST.PERLBUILD.PERL.]" I can't think of any reason to define these yourself. BUILD_PERL.COM should define all the logicals it needs. The only steps, as README.TXT says, should be: $ unzip perlbuild.zip $ set default [.perlbuild] $ submit/noprint build_perl That's it. It's entirely possible there is something goofed up in the kit, but I don't think I can narrow it down unless I'm sure we're not confusing the build by something else. The logical names defined during the build are only process logicals, so they won't affect the existing perl on your system. > >I'm having trouble linking any exe's. I looked thru the archives of >this list but didn't notice anything on this particular problem. > >Any advice is welcome, > >thanks, > >Jim Rouff >Oregon University System > >....perlbuild goes through the links > >Link /NoTrace/NoMap/Share=PERLSHR.AXE [.ext.dynaloader]dl_vms.abj, >[.ext.socket]socket.abj, []perlshr_bld.opt/Option, pe >rlshr_attr.opt/Option The only way I know of to get .AXE as an extension on your executables is to answer yes to the configuration question, "Will you be sharing your PERL_ROOT with a VAX?" And I think the only way to do that is if you run configure.com interactively, which is not what BUILD_PERL.COM does. Do you really need to have a VAX version of Perl and an Alpha version coexist in the same directory tree? >Don't know if this means anything but had a ot of "NOT found" on the >..h files I think those are normal. I haven't seen the problems you are having before and it's hard to say what might be causing them. I'd delete the perlbuild directory and start over with exactly and only the the three commands listed above and see if that gets you anywhere. Good luck, and let us know how it goes. Cheers, -- ____________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "Literary critics usually know what they're talking about. Even if they're wrong." -- Perl creator Larry Wall
