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 Message-ID: <418287B6.4060609@x-ray.at> Date: Fri, 29 Oct 2004 20:11:02 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a3) Gecko/20040817 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: snapshot cygwin1-20041026.dll misses clock_gettime() References: <41826C6C DOT 9020509 AT x-ray DOT at> <20041029163529 DOT GL29869 AT trixie DOT casa DOT cgf DOT cx> <41827EE5 DOT 7080301 AT x-ray DOT at> <20041029175103 DOT GE5890 AT trixie DOT casa DOT cgf DOT cx> In-Reply-To: <20041029175103.GE5890@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Christopher Faylor schrieb: > On Fri, Oct 29, 2004 at 07:33:25PM +0200, Reini Urban wrote: >>Christopher Faylor schrieb: >>>On Fri, Oct 29, 2004 at 06:14:36PM +0200, Reini Urban wrote: >>>>cygwin1-20041026.dll.bz2 misses clock_gettime() >>>> >>>>depends ls.exe (using msvc dependency walker) >>>> >>>>Error: At least one module has an unresolved import due to a missing >>>>export function in an implicitly dependent module. >>> >>>c:\>uname -a >>>CYGWIN_NT-5.1 norton 1.5.12s(0.116/4/2) 20041026 17:35:49 i686 unknown >>>unknown Cygwin >>>c:\>objdump -p /bin/cygwin1.dll | grep clock_gettime >>> [ 705] clock_gettime >>>c:\>ls >>>4NT CONFIG.DOS GNUPRO.BAT MSDOS.W98 SETUPXLG.TXT >>>foo run-1.1.4 >>>... >>> >>>Running "depend cygwin1.dll" shows clock_gettime in the list of functions >>>being >>>exported. >> >>well, now it works for me also... >> >>$ uname -a >>CYGWIN_NT-5.0 reini 1.5.12s(0.116/4/2) 20041026 17:35:49 i686 unknown >>unknown Cygwin >> >>no red flag anymore. > > If you are implying that I uploaded a new version of an old snapshot, I > didn't do that. I just downloaded the snapshot from the cygwin web site > and tested it. no, that problem magically went away for me without reboot. the cygwin0.dll problem - same as brian's - not yet, even after a clean build. THAT might be problem behind the keyboard. > This was apparently cockpit error on your part. cockpit is a nice word. well, the problem was not behind the keyboard. I only assume that it was some kind of timeout. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- 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/