This is the mail archive of the gcc@gcc.gnu.org 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]

Re: #import future (summary and proposed solutions)

From: Geoff Keating <geoffk at geoffk dot org>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: gcc at gcc dot gnu dot org
Date: 26 Jan 2003 21:31:21 -0800
Subject: Re: #import future (summary and proposed solutions)
References: <D1D70DEE-30F4-11D7-B2DE-0003933F3BC2@omnigroup.com><87adho76y3.fsf@egil.codesourcery.com>

Zack Weinberg <zack@codesourcery.com> writes:

> In a perfect world, file system designers would believe that stable
> inode numbers are a Good Thing.  As it is, they're basically useless
> (to FSF GCC; if Apple is prepared to guarantee that inode numbers are
> meaningful in all OSX-supported file systems, good on them).

OSX does actually try to guarantee this for UFS and HFS+
filesystems... which is why Apple development tools don't support
putting sources on network filesystems.  I don't think this is a good
approach for FSF GCC.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

References:
- Re: #import future (summary and proposed solutions)
  - From: Timothy J. Wood
- Re: #import future (summary and proposed solutions)
  - From: Zack Weinberg

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