Re: Creating lock file for compilers that don't support -c -o

[Bob Friesenhahn]

On Tue, 26 Aug 2003, Albert Chin wrote:

> On Tue, Aug 26, 2003 at 01:49:10PM +1000, Robert Collins wrote:
> > On Tue, 2003-08-26 at 12:58, Albert Chin wrote:
> >
> > > Why not use $srcfile and "$srcfile.lock" as the lock file? So, rather
> > > than:
> >
> > They may be on different fs's.
>
> How is that possible? If we use $srcfile.lock as the lock file it is
> guaranteed to be on the same filesystem as $srcfile.

The source files may be located on a read-only filesystem.  They may
also be shared (via NFS or SMB) by simultaneous builds on a number of
other hosts.  We can't/shouldn't update the source file directory or
the directory where libtool resides.  The only place we are allowed to
write is in the object directory, or the temporary file directory.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen