Front page | perl.perl5.porters |
Postings from March 2000
Re: [ID 20000330.016] Touble Installing Perl v5.6.0 on Solaris
Thread Previous
|
Thread Next
From:
Dominic Dunlop
Date:
March 31, 2000 01:19
Subject:
Re: [ID 20000330.016] Touble Installing Perl v5.6.0 on Solaris
Message ID:
p04310107b50a0a2642ab@[194.235.193.168]
At 17:30 +0100 2000-03-30, Nick Ing-Simmons wrote:
>Dan Warburton <warb@tgf.tc.faa.gov> writes:
>>I just downloaded and untarred Perl v5.6.0.
> > ...
> >lib/locale.pm: No such file or directory
>
>This is a symptom of using (say) a GNU tar compiled for SunOS4 on Solaris.
As this is becoming something of an FAQ, here's Nick's advice recast
as a patch for INSTALL (trusting that's OK, Nick):
--- perl-5.6.0/INSTALL~ Tue Mar 7 22:40:27 2000
+++ perl-5.6.0/INSTALL Fri Mar 31 10:39:12 2000
@@ -113,8 +113,38 @@
=head1 WARNING: This version requires a compiler that supports ANSI C.
-If you find that your C compiler is not ANSI-capable, try obtaining
+Most C compilers are now ANSI-compliant. However, a few current
+computers, notably from Hewlett-Packard and Sun, are delivered with an
+older C compiler expressly for rebuilding the system kernel. Such
+compilers are not suitable for building Perl. Alternatively, you may
+have an old machine which was shipped before ANSI compliance became
+widespread.
+
+If you find that your C compiler is not ANSI-capable, There are several
+avenues open to you:
+
+=over 4
+
+=item *
+
+You may try obtaining
GCC, available from GNU mirrors worldwide (e.g. ftp://ftp.gnu.org/pub/gnu).
+If, rather than building gcc from source code, you locate a
+binary version configured for your platform, be sure that it is
+compiled for version of the operating system that you are
+using.
+
+=item *
+
+You may purchase a commercial ANSI C compiler from your system
+supplier or elsewhere. (Or your organization may already have
+licensed the software -- ask your colleagues to find out how to access
+it.) If there is a README file for your system in the Perl
+distribution (for example, F<README.hpux>), it may contain advice on
+suitable compilers.
+
+=item *
+
Another alternative may be to use a tool like ansi2knr to convert the
sources back to K&R style, but there is no guarantee this route will get
you anywhere, since the prototypes are not the only ANSI features used
@@ -128,6 +158,8 @@
form, be sure to email perlbug@perl.com to let us know the steps you
followed. This will enable us to officially support this option.
+=back
+
Although Perl can be compiled using a C++ compiler, the Configure script
does not work with some C++ compilers.
@@ -1517,6 +1549,21 @@
to include the GNU utils before running Configure, or specify the
vendor-supplied utilities explicitly to Configure, for example by
Configure -Dar=/bin/ar.
+
+=item lib/locale.pm: No such file or directory
+
+This is a symptom of using (say) a GNU tar compiled for SunOS4 on
+Solaris. When you run SunOS4 binaries on Solaris the run-time system
+magically alters pathnames matching m#lib/locale# - so when tar tries
+to create lib/locale.pm a differently-named file gets created instead.
+
+You may find the file under its assumed name and be able to rename it
+back. Or use Sun's tar to do the extract.
+
+=item invalid token: ##
+
+You are using a non-ANSI-compliant C compiler. See L<WARNING: This
+version requires a compiler that supports ANSI C>.
=item Miscellaneous
--
Dominic Dunlop
Thread Previous
|
Thread Next