From owner-freebsd-current@FreeBSD.ORG Mon Jun 9 15:25:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E85DE37B401 for ; Mon, 9 Jun 2003 15:25:04 -0700 (PDT) Received: from noir.propagation.net (noir.propagation.net [63.249.159.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DF2843FA3 for ; Mon, 9 Jun 2003 15:25:04 -0700 (PDT) (envelope-from nickh@supportteam.net) Received: from dotnet (c66.169.110.87.ts46v-03.otn-a1.ftwrth.tx.charter.com [66.169.110.87]) by noir.propagation.net (8.9.3p2/8.8.5) with ESMTP id RAA25367 for ; Mon, 9 Jun 2003 17:24:51 -0500 Message-ID: <001d01c32ed5$b20cf050$0402a8c0@dotnet> From: "Nick H." To: Date: Mon, 9 Jun 2003 17:23:02 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3663.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3663.0 Subject: 5.1-RELEASE buildworld Failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2003 22:25:05 -0000 Hello, Below is a buildworld failure on a 5.1-RELEASE box with a Generic kernel: building shared library libkse.so.1 thr_libc.So: In function `sigaction': thr_libc.So(.text+0x54): multiple definition of `_sigaction' thr_sigaction.So(.text+0x0): first defined here thr_libc.So: In function `sigprocmask': thr_libc.So(.text+0x34): multiple definition of `_sigprocmask' thr_sigprocmask.So(.text+0x0): first defined here *** Error code 1 Stop in /usr/src/lib/libpthread. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have cvsup'd from the cvsup2.freebsd.org server and completely blown away the /usr/obj and /usr/src trees to repeat the process and it's producing the exact same error. Any suggestions/comments/fixes/patches are welcome. Thank you! Regards, Nick H. Network Operations Center nickh@supportteam.net