Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: well!shiva@apple.com (Kenneth Porter)
Newsgroups: comp.sys.sun
Subject: Turbo C on 386i
Keywords: 386i
Message-ID: <1383@brchh104.bnr.ca>
Date: 22 Jan 91 20:00:08 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 10, Issue 1, message 7
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

On a 386i Turbo C 2.0 and Turbo C++ 1.0 (command-line compiler, TCC.EXE)
occasionally go into an infinite compile cycle, recompiling the same file
over and over, as if they were expanding the command-line filename
argument over and over to the same value.  This happens when the directory
has many files (over 100) and is sensitive to directory order (as revealed
by "ls -f").   Moving the offending source file to another slot in the
directory (by mv-ing another file and the offending file out of the
directory and back in in the opposite order) seems to cure the problem,
but may cause a different file to fail.

Has anyone else experienced this?  Is it Borland's or Sun's fault?  Does
it occur on architectures other than the 386i?

Ken (shiva@well.sf.ca.us)