From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Collins <mcollins@wdc.sps.mot.com>
To: egcs@egcs.cygnus.com
Cc: mcollins@wdc.sps.mot.com
Subject: installation problems
Date: Fri, 30 Apr 1999 23:15:00 -0000
Message-ID: <199904232253.PAA13376@wdc.sps.mot.com>
X-SW-Source: 1999-04n/msg00833.html
Message-ID: <19990430231500.h6Q5eOxuUFWCpNRCrmrLzPpMxEctLoVIxut1-LFYvoQ@z>

  I've encountered some difficulties building and installing egcs-1.1.2
and wanted to bring them to your attention.  One was reported on Dec 15
by Hermann Hueni.  Follow-up suggestions centered around the version of
make being used, however that does not seem to be related.

  Background: make-3.77 and binutils-2.9.1 successfully built and
installed, with the paths to the resulting tools in the PATH
variable.  Bourne shell, CC variable points to gcc-2.8.1.  This
has been seen on Solaris (SunOS 5.6, UltraSPARC hardware) and Linux
(Debian 2.0 on a Pentium I).  All file systems locally mounted.

  Following the instructions included with the distribution,
I've created a build directory separate from the source tree.
On our network, we don't use the "/usr/local" convention,
so in the build directory I run the following:

  $ /p33/GNU/egcs-1.1.2/configure --prefix=/exec/gnu/elf --with-gnu-as \
  > --with-gnu-ld > Configure.log 2>&1

  In the Linux environment, I do use the "/usr/local" environment, so
my configure arguments there are:

  $ /home/mcollins/GNU/egcs-1.1.2/configure --with-gnu-as --with-gnu-ld \
    > Configure.log 2>&1

  This completes normally within a few minutes and the log file
shows no evidence of errors.  Upon completion, a number of subdirectories
and makefiles exist in the build directory.  So far, so good.

  The next step is to build the compiler:

  $ make bootstrap > Make.log 2>&1

  Again, nothing appears out of the ordinary in the log file.  Still good.

  Now to install.  I normally do everything except install as a normal
user, to limit exposure to potential disasters.

  Solaris:
  $ su root
  # make >& Install.log install

  Linux:
  $ su admin
  # make >& Install.log install

  After a few minutes, this operation comes to an end, and at the end
of the log file I see:

rm -f /exec/gnu/elf/man/man1/cccp.1
/bin/sh /p33/GNU/egcs-1.1.2/install-sh -c -m 644 /p33/GNU/egcs-1.1.2/gcc/cccp.1 
/exec/gnu/elf/man/man1/cccp.1
chmod a-x /exec/gnu/elf/man/man1/cccp.1
make: Fatal error: Don't know how to make target `f/intdoc.c'
Current working directory /p33/GNU/egcs-1.1.2-native/gcc
*** Error code 1
make: Fatal error: Command failed for target `install-gcc'

  I encountered the same difficulty with egcs-1.1.1, and also when my
command line for make omitted the "bootstrap" argument (i.e., no
explicit argument to make).

  After much experimentation, I've determined that this problem exists
because the "make install" is being run by a user who doesn't own the
source and build trees (even though, in one case, that user is root).
I was not able to isolate the cause of the problem.  I have the results
of a number of test runs available should someone wish to check my
work.

  If I "su admin" on my Linux machine before untarring the source
tree or creating a build directory, everything works and I get a good
installation.  On my Solaris machine, "make bootstrap" fails with
the following message if I "su root" before creating the source or
build trees:

Making all in makeinfo
make: Fatal error: Don't know how to make target `../lib/system.h'
Current working directory /p32/990421/Attempt_3/build/texinfo/makeinfo
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'
Current working directory /p32/990421/Attempt_3/build/texinfo
*** Error code 1
make: Fatal error: Command failed for target `all-recursive-am'
Current working directory /p32/990421/Attempt_3/build/texinfo
make: *** [all-texinfo] Error 1

  I was able to successfully build and install under Solaris only
by running configure as root directly in the source tree.  I'm not
too concerned about this problem, as I don't care to be doing more
than installing as root.  (It is probably unwise to administer
software distributions as root to begin with, however I'm limited in
the Solaris environment to the conventions of our existing network.)

  Any suggestions or remedies will be most appreciated.

				-- Mike Collins --