X-Spam-Check-By: sourceware.org Date: Sun, 18 Dec 2005 23:22:33 +0100 (MET) From: Angelo Graziosi To: cygwin AT cygwin DOT com Subject: Re: Call for testing Cygwin snapshot (d_ino) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Christopher Faylor wrote: > >> Angelo Graziosi wrote: >> >> >> I built ROOT-5.06.00, a CERN application, at Nov 10 2005 using >> GCC-3.3.3-3 and the snapshot of that time. >> >> All worked fine. >> >> Now I have repeated the build using the same method, the same >> GCC-3.3.3-3, but with the current snapshot 20051216 23:59:19. >> >> The build fails: >> >> ------------------------------------------- >> unix/src/TUnixSystem.cxx: In static member function `static const char* >> TUnixSystem::UnixGetdirentry(void*)': >> unix/src/TUnixSystem.cxx:3388: error: 'struct dirent' has no member >> named 'd_ino' >> make: *** [unix/src/TUnixSystem.o] Error 1 >> ------------------------------------------- >> >> The code that causes this error should be : >> >> ------------------------------------------- >> #if defined(_POSIX_SOURCE) >> // Posix does not require that the d_ino field be present, and some >> // systems do not provide it. >> # define REAL_DIR_ENTRY(dp) 1 >> #else >> # define REAL_DIR_ENTRY(dp) (dp->d_ino != 0) >> #endif >> ------------------------------------------- >> >> ... >> >> Is there a workaround ? > > ..... > > http://cygwin.com/ml/cygwin/2005-12/msg00205.html > > cgf If I have well understood, I should change # define REAL_DIR_ENTRY(dp) (dp->d_ino != 0) with # define REAL_DIR_ENTRY(dp) (dp->__deprecated_d_ino != 0) Is this correct? Best regards, Angelo. -- 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/