Hi All,
We have an alpha 1000, out of the box, and I am trying to install Perl.
I copied the files from the cd rom to /usr/bin/perl and ran configur and got
the messages below.
Any help appreciated
Please reply to reachus_at_netlink.uk.com by mail
Regards
Gary
/usr/bin/perl/configur
(I see you are using the Korn shell. Some ksh's blow up on Configure,
especially on exotic machines. If yours does, try the Bourne shell
instead.)
Beginning of configuration questions for perl kit.
First let's make sure your kit is complete. Checking...
cat: cannot open UU/x2p
Looks good...
Checking your sh to see if it knows about # comments...
Your sh handles # comments correctly.
Okay, let's see if #! works on this system...
It does.
Checking out how to guarantee sh startup...
Let's see if '#!/bin/sh' works...
Yup, it does.
Checking echo to see how to suppress newlines...
...using \c
Type carriage return to continue. Your cursor should be here-->
This installation shell script will examine your system and ask you
questions
to determine how the perl package should be installed. If you get stuck
on a question, you may use a ! shell escape to start a subshell or
execute
a command. Many of the questions will have default answers in square
brackets--typing carriage return will give you the default.
On some of the questions which ask for file or directory names you are
allowed to use the ~name construct to specify the login directory
belonging
to "name", even if you don't have a shell which knows about that.
Questions
where this is allowed will be marked "(~name ok)".
[Type carriage return to continue]
Much effort has been expended to ensure that this shell script will run
on any
Unix system. If despite that it blows up on you, your best bet is to
edit
Configure and run it again. Also, let me (lwall_at_netlabs.com)
know how I blew it. If you can't run Configure for some reason, you'll
have
to generate a config.sh file by hand.
This installation script affects things in two ways: 1) it may do direct
variable substitutions on some of the files included in this kit, and
2) it builds a config.h file for inclusion in C programs. You may edit
any of these files as the need arises after running this script.
If you make a mistake on a question, there is no easy way to back up to
it
currently. The easiest thing to do is to edit config.sh and rerun all
the
SH files. Configure will offer to let you do this before it runs the SH
files.
[Type carriage return to continue]
Locating common programs...
cat is in /sbin/cat.
cp is in /sbin/cp.
echo is in /usr/bin/echo.
expr is in /sbin/expr.
grep is in /sbin/grep.
mkdir is in /sbin/mkdir.
mv is in /sbin/mv.
rm is in /sbin/rm.
sed is in /usr/bin/sed.
sort is in /sbin/sort.
tr is in /usr/bin/tr.
uniq is in /usr/bin/uniq.
Don't worry if any of the following aren't found...
I don't see Mcc out there, offhand.
I don't see bison out there, either.
cpp is in /usr/bin/cpp.
csh is in /usr/bin/csh.
egrep is in /usr/bin/egrep.
line is in /usr/bin/line.
nroff is in /usr/bin/nroff.
I don't see perl out there, either.
test is in /usr/bin/test.
uname is in /usr/bin/uname.
yacc is in /usr/bin/yacc.
perl has manual pages available in source form.
If you don't want the manual sources installed, answer 'none'.
Where do the manual pages (source) go (~name ok)? [/usr/man/man1]
Hmm... Doesn't look like a MIPS system.
Where are the include files you want to use? [/usr/include]
Looks like an OSF/1 system, but we'll see...
Congratulations. You aren't running Eunice.
It's not Xenix...
Nor is it Venix...
Some systems have different model sizes. On most systems they are
called
small, medium, large, and huge. On the PDP11 they are called unsplit
and
split. If your system doesn't support different memory models, say
"none".
If you wish to force everything to one memory model, say "none" here and
put the appropriate flags later when it asks you for other cc and ld
flags.
Venix systems may wish to put "none" and let the compiler figure things
out.
(In the following question multiple model names should be space
separated.)
Which models are supported? [none] medu ium
What flag indicates medium model? [-Mm]
Use which C compiler? [cc]
Some C compilers have problems with their optimizers, by default, perl
compiles with the -O flag to use the optimizer. Alternately, you might
want to use the symbolic debugger, which uses the -g flag (on
traditional
Unix systems). Either flag can be specified here. To use neither flag,
specify the word "none".
What optimizer/debugger flag should be used? [-O]
Your C compiler may want other flags. For this question you should
include -I/whatever and -DWHATEVER flags and any other flags used by
the C compiler, but you should NOT include libraries or ld flags like
-lwhatever. For instance, this would be a good place to specify
-DDEBUGGING. To use no flags, specify the word "none".
Any additional cc flags? [ -DLANGUAGE_C]
(C preprocessor flags: -DLANGUAGE_C)
Any additional ld flags (NOT including libraries)? [none]
Checking for optional libraries...
No -lc_s.
No -lnet_s.
No -lnet.
No -lsocket.
No -lnsl_s.
No -lnsl.
No -lnm.
No -lndir.
No -ldir.
No -lndbm.
Found -ldbm.
Found -lPW.
No -lmalloc.
No -lsun.
Found -lm.
Found -lbsd.
No -lBSD.
No -lx.
No -lposix.
No -lucb.
Some versions of Unix support shared libraries, which make
executables smaller but make load time slightly longer.
On some systems, mostly newer Unix System V's, the shared library
is included by putting the option "-lc_s" as the last thing on the
cc command line when linking. Other systems use shared libraries
by default. There may be other libraries needed to compile perl
on your machine as well. If your system needs the "-lc_s" option,
include it here. Include any other special libraries here as well.
Say "none" for none.
Any additional libraries? [-ldbm -lPW -lm -lbsd]
Checking alignment constraints...
Doubles must be aligned on a how-many-byte boundary? [8]
The following questions distinguish the directory in which executables
reside from the directory in which they are installed (and from which
they
are presumably copied to the former directory by occult means). This
distinction is often necessary under afs. On most other systems,
however,
the two directories are the same.
In which directory will public executables reside (~name ok)?
[/usr/lbin]
In which directory will public executables be installed (~name ok)?
[/usr/lbin]
In the following, larger digits indicate more significance. A
big-endian
machine like a Pyramid or a Motorola 680?0 chip will come out to 4321.
A
little-endian machine like a Vax or an Intel 80?86 chip would be 1234.
Other
machines may have weird orders like 3412. A Cray will report 87654321.
If
the test program works the default is probably right.
I'm now running the test program...
(The test program ran ok.)
What is the order of bytes in a long? [12345678]
Checking to see if your C compiler can cast weird floats to unsigned
Yup, it does.
Now, how can we feed standard input to your C preprocessor...
Maybe "cc -E" will work...
configur: testcpp.c: cannot open
Nope...maybe "cc -E -" will work...
configur: testcpp.c: cannot open
No such luck, maybe "/usr/bin/cpp" will work...
configur: testcpp.c: cannot open
Nixed again...maybe "/usr/bin/cpp -" will work...
configur: testcpp.c: cannot open
Uh-uh. Time to get fancy. Trying a wrapper...
configur: testcpp.c: cannot open
Nope...maybe "cc -P" will work...
configur: testcpp.c: cannot open
Nope...maybe "cc -P -" will work...
configur: testcpp.c: cannot open
No dice. I can't find a C preprocessor. Name one: configur: myread:
not found
#
Received on Fri Oct 11 1996 - 16:14:44 NZDT