Path: utzoo!attcan!uunet!elroy.jpl.nasa.gov!sdd.hp.com!hplabs!hpfcso!chance
From: chance@hpfcso.FC.HP.COM (Chance Brohm)
Newsgroups: comp.soft-sys.andrew
Subject: HP9000 && #undef LINKINSTALL_ENV broken?
Message-ID: <8450003@hpfcso.FC.HP.COM>
Date: 12 Feb 91 06:34:41 GMT
Organization: Hewlett-Packard, Fort Collins, CO, USA
Lines: 34

Howdy! I'm trying to build the latest Andrew software on an HP9000 running
HP-UX 7.0. I got patchlevel 7 working without too much trouble; there was a
problem where the C preprocessor was sticking in line numbers (for debugging)-
I fixed that with an "IMAKEINCLUDE='-I. -P'" environment variable. (The -I.
part is there because imake wants the string to start -I...). Once set, the
build ran fine and I had Andrew running pretty well. Then I moved to a new
system (my own...now I can try out AMDS & SNAP!) and decided to build anew
with the latest patchkit.

I got pretty far with patchlevel 9 (current, right?) - that is, until I ran
out of disk space. So, I moved the source tree to another system (mounted
via NFS), put an "#undef LINKINSTALL_ENV" in my site.h and rebuilt. Making
the Makefiles seemed to go OK (no fatal errors), but when I got to doing
a "make dependInstall" it looks like my attempt to turn LINKINSTALL off
failed. The first directory was andrew/install - it created a bunch of
symbolic links (eg., "ln -s ../include/andrewos.h andrewos.h") in the
/usr/andrew/config directory, but the targets of the symlinks don't exist
(in fact, the only thing in /usr/andrew/include is site.h). Then, when it
got to a later directory (andrew/overhead/sys) makedepend complained that
it can't open andrewos.h (surprise!) and the build recursively suicided like
so many dominoes.

Question: should this work? Is it correct that all I have to do to have the
source tree independent from the install tree is to undefine LINKINSTALL_ENV?
(Personally, I prefer the "get a bigger disk" solution, but it's not an
option at this point.) I could probably hand-copy the include files over and
get the build to continue (for how long?), but I bet this is a symptom of
a bigger problem.

Any suggestions/solutions gratefully accepted!
 -Chance

P.S. I'll check this newsgroup for responses; if you would prefer to contact
me via Email, feel free to write me at chance@fc.hp.com.  Thanks! -CB