X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 6 Aug 2010 18:39:25 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: The dirent struct Message-ID: <20100806163925.GE31783@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20100806134005 DOT GD22459 AT ednor DOT casa DOT cgf DOT cx> <20100806141140 DOT GC31783 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Aug 6 10:51, Chris Sutcliffe wrote: > On 6 August 2010 10:11, Corinna Vinschen wrote: > > On Aug  6 09:40, Christopher Faylor wrote: > >> On Fri, Aug 06, 2010 at 09:33:41AM -0400, Chris Sutcliffe wrote: > >> >I assume d_fileno and d_reclen may be part of __d_unused1 or > >> >__d_internal1?  I'd appreciate some help here, since I'm not sure what > >> >to do at this point. > >> > >> No, they are not part of either of those fields.  If they were > >> they would be exposed. > >> > >> They simply are not implemented. > > > > And they don't have to.  Per POSIX, only d_ino and d_name can be > > expected by a portable application(*). > > Fair enough, thankfully they are don't seem to be used by the code, so > I added an '#ifndef __CYGWIN__' around them and have managed to get by > this. Btw., d_fileno is just another old name for d_ino. The Linux headers defines it thus as `#define d_fileno d_ino'. We can do the same in Cygwin. Maybe that minimizes some porting effort. As for d_reclen, there was a discussion already at one point: http://cygwin.com/ml/cygwin/2009-09/msg00023.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple