This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: 3.2 PATCH: Document PWDCMD
Gerald Pfeifer writes:
> On Thu, 16 May 2002, Rainer Orth wrote:
> > As requested, the ability to use PWDCMD to avoid various automounter
> > problems should be documented.
>
> Interestingly, having used automounts on Solaris 2.6 and 8 as well
> as FreeBSD 3.x and 4.x for years, I've never had a single problem.
It certainly depends on the configuration: Solaris 2 automount (with kernel
AutoFS support) isn't affected since mounts are done in place. On the
other hand, traditional automounters (like automount or amd) are affected,
the details heavily depend on the circumstances: we have source and object
trees on different file systems, and it regularly happens that the source
tree is unmounted in the middle of a build since the build system only uses
the physical pathnames, thus amd is not aware of accesses and unmounts the
FS. Other (hard to diagnose) problems occured since logical and physical
pathnames were compared and didn't match.
> > +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
>
> Perhaps "Using these"?
Ok.
> > @command{amq -w}
>
> Our am-utils version 6.0.3s1 here don't support this, but I assume you
> have seen this on some previous or later versions?
It's an addition from amd 6.0.4.
> > Thu May 16 21:16:40 2002 Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
> >
> > * doc/install.texi (Configuration): Document PWDCMD.
>
> Looks fine, thanks!
Thanks, installed.
Rainer