This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

3.2 PATCH: Document PWDCMD

As requested, the ability to use PWDCMD to avoid various automounter
problems should be documented.  The patch below does so; tested with make
gccinstall.dvi and

Ok for mainline?


Thu May 16 21:16:40 2002  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>

	* doc/install.texi (Configuration): Document PWDCMD.

Index: install.texi
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.116
diff -u -p -r1.116 install.texi
--- install.texi	14 May 2002 10:38:46 -0000	1.116
+++ install.texi	16 May 2002 20:15:04 -0000
@@ -279,6 +279,14 @@ GCC; we use @var{objdir} to refer to the
 If you obtained the sources via CVS, @var{srcdir} must refer to the top
 @file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
 and not its @file{gcc} subdirectory, otherwise the build will fail.
+If either @var{srcdir} or @var{objdir} is located on an automounted NFS
+file system, the shell's built-in @command{pwd} command will return
+temporary pathnames.  Using them can lead to various sorts of build
+problems.  To avoid this issue, set the @env{PWDCMD} environment
+variable to an automounter-aware @command{pwd} command, e.g.,
+@command{pawd} or @command{amq -w}, during the configuration and build
 First, in general, GCC @strong{must} be built into a separate directory
 than the sources which does @strong{not} reside within the source tree.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]