Continuing my last mail about doubting why my compilation of perl5_6_1
on vms alpha 7.1,alpha 7.21, and vax 7.1 show system() problem and the
downloaded binary perl5.6(s) do not show the problem(I even set file
version limit to more than 1, and did not get a second version for
temp2.tmp), I wonder whether I did something wrong in my configuration.
In my last test, I chose all *default* in @configure.com procedure, and the
following is a log of the configuration. Any suggestions/analysis of this
log file will be appreciated.
Thanks,
June Young
-----------------
>A:..ACTIVE.PERL-5_6_1> @configure
>
>Beginning of configuration questions for perl5.
>
>
>First let's make sure your kit is complete. Checking...
>Looks good...
>
>This installation shell script will examine your system and ask you questions
>to determine how the perl5 package should be installed. If you get
>stuck on a question, you may use a ^C or ^Y shell escape to STOP this
>process, edit something, then restart this process as you just did.
>Many of the questions will have default answers in square
>brackets; typing carriage return will give you the default.
>
>Type carriage return to continue
>
>In a hurry? You may run '@Configure "-d"'. This will bypass nearly all
>the questions and use the computed defaults (or the previous answers provided
>there was already a config.sh file). Type '@Configure "-h"' for a list of
>options.
>
>Type carriage return to continue
>
>Much effort has been expended to ensure that this shell script will
>run on any VMS system. If despite that it blows up on yours, your
>best bet is to edit Configure.com and @ it again. Whatever problems
>you have with Configure.com, let me ([EMAIL PROTECTED]) know how I blew
>it.
>
>Type carriage return to continue
>
>Configure uses the operating system name and version to set some defaults.
>The default value is probably right if the name rings a bell. Otherwise,
>since spelling matters for me, either accept the default or answer "none"
>to leave it blank.
>
>Operating system name? [VMS]
>
>According to the setting of your "SYS$TIMEZONE_DIFFERENTIAL" (= -10800)
>Your system is 3 hours west of UTC in England.
>
>(-10800) Is this UTC Time Zone Offset correct? [y]
>
>What is your architecture name? [VMS_AXP]
>
>Will you be sharing your PERL_ROOT with a VAX? [n]
>
>By default, perl5 will be installed in DSA0:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1.], pod
>pages under DSA0:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1.LIB.POD], etc..., i.e. with
>DSA0:[DYMAX.PERL5006_ACTIVE.PERL
>-5_6_1.] as prefix for
>all installation directories.
>On VMS the prefix is used to DEFINE the PERL_ROOT prior to installation
>as well as during subsequent use of perl5 via PERL_SETUP.COM.
>
>Installation prefix to use (for PERL_ROOT)? [
>DSA0:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1.] ] [DYMAX.PERL5006_ACTIVE
>.PERL56_72]
>
>Skip the remaining "where install" questions? [y]
>
>You may choose to write PERL_SETUP.COM to assign a foreign
>symbol to invoke perl5, which is the usual method.
>If you do not do so then you would need a DCL command verb at the
>process or the system wide level.
>
>Invoke perl as a global symbol foreign command? [y]
>
>Getting the current patchlevel...
>(You have perl5 revision 5 patchlevel 6 subversion 1.)
>
>There is, however, a strange, musty smell in the air that reminds me of
>something...hmm...yes...I've got it...there's a VMS nearby, or I'm a Blit.
>
>Default "cc" is DEC C V6.0-001 AXP V7.1-2
>Checking for gcc
>Available compiler(s):
>( cc/decc )
>
>Use which C compiler? [cc/decc]
>
>Checking for the Dec C version number...
>You are using Dec C 60090001
>
>Figuring out host name...
>
>Your host name appears to be "dyma.dymaxion.ca". Right?
>
>What is your domain name? [.dymaxion.ca]
>(Trimming domain name from host name--host name is now dyma)
>
>I need to get your e-mail address in Internet format if possible, i.e.
>something like [EMAIL PROTECTED] Please answer accurately since I have
>no easy means to double check it. The default value provided below
>is most probably close to the reality but may not be valid from outside
>your organization...
>
>What is your e-mail address? [[EMAIL PROTECTED]]
>
>If you or somebody else will be maintaining perl at your site, please
>fill in the correct e-mail address here so that they may be contacted
>if necessary. Currently, the "perlbug" program included with perl
>will send mail to this address in addition to [EMAIL PROTECTED] You may
>enter "none" for no administrator.
>
>Perl administrator e-mail address [[EMAIL PROTECTED]]
>
>Hmm... Looks like you have Dec C Berkeley networking support.
>
>You have sockets available. Which socket stack do you want to
>build into Perl?
>
>Choose socket stack (NONE,DECC) [DECC]
>
>Perl can be built to run under the VMS debugger.
>You should only select this option if you are debugging
>perl itself. This can be a useful feature if you are
>embedding perl in a program.
>
>Build a VMS-DEBUG version of Perl? [n]
>
>Perl can be built with extra runtime debugging enabled. This
>enables the -D switch, at the cost of some performance. It
>was mandatory on perl 5.005 and before on VMS, but is now
>optional. If you do not generally use it you should probably
>leave this off and gain a bit of extra speed.
>
>Build a DEBUGGING version of Perl? [y]
>
>Perl can be built so that multiple Perl interpreters can coexist
>within the same Perl executable.
>There is some performance overhead, however, so you
>probably do not want to choose this unless you are going to be
>doing things with embedded perl.
>
>Build Perl for multiplicity? [n]
>
>You can have native 64-bit long integers.
>
>Perl can be built to take advantage of 64-bit integer types
>on some systems, which provide a much larger range for perl's
>mathematical operations. (Note that does *not* enable 64-bit
>fileops at the moment, as Dec C doesn't do that yet).
>Choosing this option will most probably introduce binary incompatibilities.
>
>If this does not make any sense to you, just accept the default n.
>
>Try to use 64-bit integers, if available? [n]
>
>This version of Perl can be built with threads. While really nifty,
>they are a beta feature, and there is a speed penalty for perl
>programs if you build with threads *even if you do not use them*.
>
>Build with threads? [n]
>
>By default, perl (and pretty much everything else on VMS) uses
>case-insensitive linker symbols. Which is to say, when the
>underlying C code makes a call to a routine called Perl_foo in
>the source, the name in the object modules or shareable images
>is really PERL_FOO. There are some packages that use an
>embedded perl interpreter that instead require case-sensitive
>linker symbols.
>
>If you have no idea what this means, and do not have
>any program requiring anything, choose the default.
>
>Build with case-sensitive symbols? [n]
>
>Perl normally uses G_FLOAT format floating point numbers
>internally, as do most things on VMS. You can, however, build
>with IEEE floating point numbers instead if you need to.
>
>Use IEEE math? [n]
>
>Your compiler may want other flags. For this question you should include
>/INCLUDE=(whatever) and /DEFINE=(whatever), flags and any other flags
>or qualifiers used by the compiler.
>
>To use no flags, specify the word "none".
>
>Any additional cc flags? []
>
>As Perl starts up, it checks several logical names, such as
>PERL5LIB and PERL_ENV_TABLES, which allow you to modify aspects
>of its behavior. For additional security, you may limit this
>process to executive- and kernel-mode translation when tainting
>is enabled. In this case, logical names normally skipped when
>tainting is enabled (e.g. PERL5OPTS) are translated as well.
>If you do not choose to do this, the usual order of access modes
>is used for logical name translation.
>
>This restriction does not apply to the %ENV hash or to implicit
>logical name translation during parsing of file specifications;
>these always use the normal sequence of access modes for logical
>name translation.
>
>Use secure logical name translation? [y]
>
>When you pass the name of a program to Perl on the command line,
>it generally doesn't supply any defaults unless the -S command
>line switch is specified. In keeping with the VMS tradition of
>default file types, however, you can configure Perl to try default
>file types of nothing, .pl, and .com, in that order (e.g. typing
>"$ perl foo" would cause Perl to look for foo., then foo.pl, and
>finally foo.com).
>
>This is currently broken in some configurations. Only enable it if
>you know what you are doing.
>
>Always use default file types? [n]
>
>Perl has a built-in memory allocator that is tuned for normal
>memory usage. It is oftentimes better than the standard system
>memory allocator. It also has the advantage of providing memory
>allocation statistics, if you choose to enable them.
>
>Do you wish to attempt to use the malloc that comes with perl5? [n]
>
>It is time to specify which modules you want to build into
>perl. Most of these are standard and should be chosen, though
>you might, for example, want to build GDBM_File instead of
>SDBM_File if you have the GDBM library built on your machine.
>
>Which modules do you want to build into perl?
>
>[re Fcntl Errno File::Glob IO Opcode Devel::Peek Devel::DProf Data::Dumper attrs
>VMS::Stdio VMS::DCLsym B SDBM_
>File Thread Sys::Hostname POSIX]
>
>Checking your "make" utilities...
>Testing whether you have IMAKE on your system...
>Nope.
>Testing whether you have GNUMAKE on your system...
>Nope.
>Testing whether you have MGMAKE on your system...
>Nope.
>Testing whether you have GMAKE on your system...
>Nope.
>Testing whether you have MAKE on your system...
>%MAKE, -f doesn't exist and couldn't be made.
>Nope.
>Testing whether you have MMS on your system...
>OK.
>Testing whether you have MMK on your system...
>OK.
>
>Here is the list of builders you can apparently use:
>( MMS MMK )
>
>Which "make" utility do you wish to use? [MMK]
>
>What pager is used on your system? [most]
>
>Checking the C run-time library.
>Your C compiler and pre-processor defines the symbol:
>__STDC__
>Checking to see how big your double precision numbers are...
>Your double is 8 bytes long.
>Checking to see if you have long double...
>You have long double.
>Checking to see how big your long doubles are...
>Your long doubles are 16 bytes long.
>Checking to see if you have long long...
>You have long long.
>Checking to see how big your long longs are...
>Your long longs are 8 bytes long.
>Looking for the type for group ids returned by getgid().
>gid_t found.
>Looking for the type for dev.
>dev_t found.
><unistd.h> found.
><libutil.h> NOT found.
><shadow.h> NOT found.
><socks.h> NOT found.
>select() found.
>Checking to see how well your C compiler handles fd_set and friends ...
>Well, your system knows about the normal fd_set typedef...
><inttypes.h> found.
>Checking to see if you have off64_t...
>You do not have off64_t.
>Checking to see if you have fpos64_t...
>You do not have fpos64_t.
>Checking to see if you have int64_t...
>You have int64_t.
><netdb.h> found.
>Checking to see if you have h_errno...
>You have h_errno.
>gethostname() found.
><sys/file.h> found.
><sys/utsname.h> found.
><syslog.h> NOT found.
><poll.h> NOT found.
><sys/uio.h> found.
><sys/mode.h> NOT found.
><sys/access.h> NOT found.
><sys/security.h> NOT found.
><fcntl.h> found.
>fcntl() found.
>Checking if fcntl-based file locking works...
>Nope, it didn't work.
>memchr() NOT found.
>strtoull() found.
>strtouq() found.
>strtoll() found.
>strtold() NOT found.
>atoll() found.
>atolf() NOT found.
>acess() NOT found.
>bzero() found.
>bcopy() found.
>mkstemp() found.
>mkstemps() NOT found.
><iconv.h> found.
>mkdtemp() NOT found.
>setvbuf() found.
>setenv() found.
>setproctitle() NOT found.
><netinet/in.h> found.
><netinet/tcp.h> found.
>endhostent() found.
>endnetent() found.
>endprotoent() found.
>endservent() found.
>sethostent() found.
>setnetent() found.
>setprotoent() found.
>setservent() found.
>gethostent() found.
>getnetent() found.
>getprotoent() found.
>getservent() found.
>Checking to see if you have socklen_t...
>You do not have socklen_t.
>Checking to see how big your pointers are...
>Your pointers are 4 bytes long.
>Checking the size of size_t...
>Your size_t size is 4 bytes.
>Looking for a random number function...
>Good, found drand48().
>Choosing the C types to be used for Perl's internal types...
>(IV will be "long", 4 bytes)
>(UV will be "unsigned long", 4 bytes)
>(NV will be "double", 8 bytes)
>Checking whether your NVs can preserve your UVs...
>Yes, they can.
>Creating CONFIG.SH...
>
>If you'd like to make any changes to the config.sh file before I begin
>to configure things, answer yes to the following question.
>
>
>Do you wish to edit CONFIG.SH? [n] y
>
>Be sure to type LOGOUT after you have edited the file,
>then this procedure will resume.
>
>
>Directory DSA0:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1]
>
>CONFIG.SH;1
>
>Total of 1 file.
>
>[redirected sitelibexp to our own library path here]
>
>A:..ACTIVE.PERL-5_6_1> lo
> Process JY_1 logged out at 10-JUL-2001 04:44:01.72
>
> Accounting information:
> Buffered I/O count: 1535 Peak working set size: 4720
> Direct I/O count: 95 Peak virtual size: 171152
> Page faults: 926 Mounted volumes: 0
> Charged CPU time: 0 00:00:00.15 Elapsed time: 0 00:00:27.91
>%DCL-S-RETURNED, control returned to process JY_04
>
>Adding VMS specific preprocessor commands.
>Doing variable substitutions on .SH files...
>Extracting config.h (with variable substitutions)
>Extracting DESCRIP.MMS (with variable substitutions)
>Extracting make_ext.com (without variable substitutions)
>Extracting extra_pods.com (without variable substitutions)
>
>Checking for dangerous pre-existing global symbols and logical names.
>
>The perl_setup.com file is now being written...
>
>The file can be found at:
> DSA0:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1]PERL_SETUP.COM;1
>Add that file (or an @ call to it) to your [SY]LOGIN.COM
>when you are satisfied with a successful compilation,
>testing, and installation of your perl.
>
>
>In order to build perl5 you must now issue the command:
>
> MMK
>
>Hmm. I also noted the following information while running:
>
>
>Logical name T found in environment as
>DYM$SOURCE:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1.HARNESS]
> deassign before building perl5
>A:..ACTIVE.PERL-5_6_1>
>
>
>--
>June Young, Software Development bus: (902)422-1973 x144
>Dymaxion Research Ltd., 5515 Cogswell St., fax: (902)421-1267
>Halifax, Nova Scotia, B3J 1R2 Canada mailto: [EMAIL PROTECTED]
> http://www.dymaxion.ca
--
June Young, Software Development bus: (902)422-1973 x144
Dymaxion Research Ltd., 5515 Cogswell St., fax: (902)421-1267
Halifax, Nova Scotia, B3J 1R2 Canada mailto: [EMAIL PROTECTED]
http://www.dymaxion.ca
