Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Unresolved clock_settime
Date: Thu, 14 Apr 2005 12:02:37 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <200504141054.j3EAsAUV028749@thor.remedy.nl>
Message-ID: <SERRANOAddX47sFoai800000145@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 14 Apr 2005 11:02:39.0258 (UTC) FILETIME=[790C0FA0:01C540E1]

----Original Message----
>From: Johnny Willemsen
>Sent: 14 April 2005 11:54

> Hi,
> 
> We use clock_gettime and clock_settime. We now get an undefined reference
> when linking on clock_settime, clock_gettime doesn't give any problems.
> Someone an idea?
> 


  There is no clock_settime in cygwin.  Never has been from what I can see.
clock_* support is incomplete in cygwin.  http://cygwin.com/acronyms#PTC !



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/