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 Date: Thu, 2 Mar 2000 01:54:49 -0500 (EST) From: Charles Wilson X-Sender: cwilson AT frontal DOT ibb DOT gatech DOT edu To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: build problems In-Reply-To: <38B4E41C.A9794665@ece.gatech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Okay, THIS is the thread to which the following reply should have been attached. FWIW, the problems described below were fixed with the Feb 28 snapshot. That includes the 100% usage problem and the weird configure failures when building. --Chuck On Thu, 24 Feb 2000, Charles S. Wilson wrote: > After updating to Feb 4 cygwin1.dll, I can no longer build many packages > that rely on configure; it seems to have something to do with file > access. Since Corinna pointed out the missing filemode in the open() > call in cygipc, I discovered more missing filemodes in the open() calls > in gdbm. > > Okay, so I added filemode bits to cygipc (I'll upload v1.05 soon) and > was able to build it -- cygipc does not use configure (e.g. autoconf, > etc). However, when I made similar fixes to gdbm, I got the following > errors when I ran configure: > > cwilson : belgarion : /usr/local/src/gdbm-1.8.0-1 > ./configure > > ... > checking for off_t... yes > checking for st_blksize in struct stat... yes > updating cache ./config.cache > creating ./config.status > creating Makefile > sed: can't read /Makefile.in: No such file or directory > creating autoconf.h > cat: /autoconf.h.in: No such file or directory > autoconf.h is unchanged > > cwilson : belgarion : /usr/local/src/gdbm-1.8.0-1 > > > I've also seen these problems with bash-2.0.3 and make-3.78 -- "sed: > can't read /foo: No such file or directory". Anyway, reverting to the > 20000131 cygwin1.dll eliminates these problems. Using the 20000223 > cygwin1.dll failed, but for a different reason -- bash got hung while > reading the .dotfiles. Has anyone seen this build/configure problem > before? What's going on? > > --Chuck > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com