Basically, I asked why a compiler install was a prereq for installing
PERL. (Original query attached.)
And Caspar's answer:
"This happens because perl generates many dependencies in the Makefiles;
you cannot fix it w/o removing the dependencies from the Makefiles."
I conclude that I would need to do substantial work in the PERL src tree
in order to accomplish what I want.
Other correspondents pointed out work-arounds, ranging from using pkg'ed
versions of PERL to automounting the entire /usr/local tree (or enough of
it to handle the compiler header dependencies).
Thanks to:
Parkhaev Vladimir
Halverson, Mark
robsonk@ebrd.com
Xu, Ying X.
Kevin M. Korb
Arthur Darren Dunham
Bertrand_Hutin
Mark Luntzel
David Foster
Eric
---------- Forwarded message ----------
Date: Tue, 29 Feb 2000 05:54:01 -0800 (PST)
From: Stuart Kendrick <sbk@fred.fhcrc.org>
To: sun-managers@sunmanagers.ececs.uc.edu
Subject: PERL and limits.h
Hi,
I've run into a nit installing PERL.
I compile perl5.005_03 on my compile host. Works fine.
I automount compile-host:/opt/local/src across my entire collection of
machines. That way, I can type "cd /opt/local/src/{random package}; make
install" from any machine and install binaries.
When I go to a random machine, "df-umx" in this case, and type "make
install", I see the following:
df-umx% make install
make: Warning: Both `makefile' and `Makefile' exist
make: Fatal error: Don't know how to make target
`/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/include/limits.h'
df-umx%
If I install my compiler on the relevant box, "df-umx", in this case, then
the "make install" proceeds just fine. I've replicated this issue with
previous versions of PERL, in the 5.00x lineage.
I would prefer not to install gcc on every single box I own, purely in
order to install PERL.
Insights?
Solaris 2.7, gcc-2.95.1
--sk
Stuart Kendrick
FHCRC
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:04 CDT