From owner-freebsd-stable Sun Aug 4 13:55:32 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 73EF437B400; Sun, 4 Aug 2002 13:55:30 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8D4843E3B; Sun, 4 Aug 2002 13:55:29 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g74KtSL3019742; Sun, 4 Aug 2002 16:55:28 -0400 (EDT) Date: Sun, 4 Aug 2002 16:55:28 -0400 (EDT) From: Daniel Eischen To: "Justin T. Gibbs" Cc: deischen@FreeBSD.org, stable@FreeBSD.org Subject: Re: uthread_dup2.c and __sys_close In-Reply-To: <200208041912.g74JCMSY060357@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message