From owner-freebsd-stable Sun Aug 4 14: 6:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A72C337B400; Sun, 4 Aug 2002 14:06:27 -0700 (PDT) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9C1143E5E; Sun, 4 Aug 2002 14:06:26 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.12.5/8.12.5) with ESMTP id g74L6OSY057682; Sun, 4 Aug 2002 15:06:24 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200208042106.g74L6OSY057682@aslan.scsiguy.com> To: Daniel Eischen Cc: deischen@FreeBSD.org, stable@FreeBSD.org Subject: Re: uthread_dup2.c and __sys_close In-Reply-To: Your message of "Sun, 04 Aug 2002 16:55:28 EDT." Date: Sun, 04 Aug 2002 15:06:24 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >On Sun, 4 Aug 2002, Justin T. Gibbs wrote: >> I was just trying to build XFree86 from the latest cvsup'ed sources >> and ran into a build error do to an unresolved reference to __sys_close >> in libc_r. I tracked this down to uthread_dup2.c which seems to have >> a stray __sys_close call in it. Changing this to _thread_sys_close(), >> as is done in uthread_dup.c, appears to have cleared up the problem. >> Is this a correct fix? > >Yes, but the botched MFC was fixed in rev 1.9.2.3 which was committed >on Friday sometime. Did you cvsup prior to that? Yes. Sorry for the noise. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message