Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 27 Apr 2000 14:13:21 -0400 To: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: Re: Weird behavior when using "-I" with gcc-2.95.2 Message-ID: <20000427141321.B1434@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, "'cygwin AT sourceware DOT cygnus DOT com'" References: <7B4C28C84831D211BFA200805F9F34567030F7 AT nswcdlvaex04 DOT nswc DOT navy DOT mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Thu, Apr 27, 2000 at 01:09:45PM -0500 On Thu, Apr 27, 2000 at 01:09:45PM -0500, Mumit Khan wrote: >On Thu, 27 Apr 2000, Fontenot Larry A DLVA wrote: >> Well that was very interesting. Everything compiles just fine on the local >> hard disk when using the "-I ./". So then I tried my H:\ drive. That is a >> drive I have mapped from a WinNT server. Once again, everything works just >> fine. So then I went to my I:\ drive, which is a Sun Solaris file server >> using SunLink software to emulate a WinNT server. That is when I start >> having problems. Apparently, gcc is seeing something differently when >> compiling on my I:\ drive. Should I try to use strace at this point to find >> out what the difference might be? > >Normally I'd blame inode generation on remote drives, but that's not it >since I've turned off inode based path lookup optimization in gcc. > >It does look like a problem with Cygwin interaction with SunLink (I know >nothing of this software). Now that we know where the problem lies, we >should try to isolate it by writing the shortest possible testcase. Maybe >a problem with `stat' on SunLink server? > >I suppose the strace output may be a good place to start. It's going to be >large, so do compress the output using gzip before posting. Hopefully the >Cygwin gurus can take over and solve this mystery. Can we at least try the latest snapshot first? cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com