Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 22 Apr 2005 09:13:10 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: findutils still broken
Message-ID: <20050422131310.GF16791@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <042120052015 DOT 18583 DOT 426809E50001CC150000489722070009530A050E040D0C079D0A AT comcast DOT net> <20050421202823 DOT GB4887 AT trixie DOT casa DOT cgf DOT cx> <20050422083750 DOT GC7692 AT cygbert DOT vinschen DOT de> <20050422114949 DOT GB16791 AT trixie DOT casa DOT cgf DOT cx> <20050422123758 DOT GF3485 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050422123758.GF3485@cygbert.vinschen.de>
User-Agent: Mutt/1.5.8i

On Fri, Apr 22, 2005 at 02:37:58PM +0200, Corinna Vinschen wrote:
>On Apr 22 07:49, Christopher Faylor wrote:
>> On Fri, Apr 22, 2005 at 10:37:50AM +0200, Corinna Vinschen wrote:
>> >I'm not sure this presumption is correct.  The d_ino field is not marked
>> >as optional in SUSv3, it's marked as an XSI extension.  The crux with
>> >XSI extensions is that (quote SuSv3) "Application writers may confidently
>> >make use of an extension on all systems supporting the X/Open System
>> >Interfaces Extension."  This covers practically every serious system in
>> >the POSIX world right now.  If we drop d_ino, I'd expect another round
>> >of suddenly broken applications.
>> 
>> If there are programs out there which rely on d_ino then they are broken
>> on cygwin right now and have been for some time.
>
>It's more the existance than the correctness what I'm taking about.
>I can easily imagine applications using d_ino only for keeping track
>of directory content.  Mind you, I'm just concerned that dropping
>the struct member could affect applications.  OTOH, that's what porting
>is for, isn't it?

Right.  For the uninitiated, here's how porting works in cygwin land:

  Step one - notice that you want something.

  Step two - send email to the cygwin list asking where it is.

  Step three - download the package.

  Step four - send email to the cygwin list asking what a .tar.gz,
  .tar.bz2, or .tgz file is.

  Step five - unpack the file.

  Step six - send email to the cygwin list asking if anyone knows
  how to build the package.

  Step seven - type configure; make.

  Step eight - report all compilation errors to the cygwin list.

  Step nine - report the same errors after waiting a few hours.

  Step ten - send email from another account asking roughly the same
  question.

  Step eleven - wait a couple of days and resubmit the email under
  a different subject.

  Step twelve - make some of the changes that were suggested on the list.

  Step thirteen - goto seven.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/