From owner-freebsd-current@FreeBSD.ORG Wed Mar 29 02:01:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 4CF4716A400; Wed, 29 Mar 2006 02:01:43 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EA2B43D48; Wed, 29 Mar 2006 02:01:41 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FOQ58-0007cB-Q6; Wed, 29 Mar 2006 11:06:48 +0900 Message-ID: <4429EA92.9070501@micom.mng.net> Date: Wed, 29 Mar 2006 11:01:54 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20060328200624.GA10800@xor.obsecurity.org> <20060328211231.GB1968@xor.obsecurity.org> In-Reply-To: <20060328211231.GB1968@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: deischen@freebsd.org, Kris Kennaway Subject: Re: libpthread compile failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 29 Mar 2006 02:01:43 -0000 Hi, I've got some errors on todays's CURRENT. How can I fix this quickly? cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/librt/../libc/include -I/usr/src/lib/librt -Winline -Wall -g -c /usr/src/lib/librt/timer.c cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/librt/../libc/include -I/usr/src/lib/librt -Winline -Wall -g -c /usr/src/lib/librt/timer.c -o timer.So /usr/src/lib/librt/sigev_thread.c: In function `have_threads': /usr/src/lib/librt/sigev_thread.c:105: error: `pthread_create' undeclared (first use in this function) /usr/src/lib/librt/sigev_thread.c:105: error: (Each undeclared identifier is reported only once /usr/src/lib/librt/sigev_thread.c:105: error: for each function it appears in.) /usr/src/lib/librt/sigev_thread.c: In function `sigev_thread_create': /usr/src/lib/librt/sigev_thread.c:336: warning: implicit declaration of function `pthread_create' /usr/src/lib/librt/sigev_thread.c: In function `have_threads': /usr/src/lib/librt/sigev_thread.c:105: error: `pthread_create' undeclared (first use in this function) /usr/src/lib/librt/sigev_thread.c:105: error: (Each undeclared identifier is reported only once /usr/src/lib/librt/sigev_thread.c:105: error: for each function it appears in.) /usr/src/lib/librt/sigev_thread.c: In function `sigev_thread_create': /usr/src/lib/librt/sigev_thread.c:336: warning: implicit declaration of function `pthread_create' *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error Ganbold Kris Kennaway wrote: > On Tue, Mar 28, 2006 at 04:09:10PM -0500, Daniel Eischen wrote: > >> On Tue, 28 Mar 2006, Kris Kennaway wrote: >> >> >>> On 7.0 during buildworld: >>> >>> /usr/src/lib/libpthread/thread/thr_barrier.c:69: error: conflicting types for '_pthread_barrier_init' >>> /usr/src/lib/libpthread/../../include/pthread.h:156: error: previous declaration of '_pthread_barrier_init' was here >>> /usr/src/lib/libpthread/thread/thr_barrier.c:69: error: conflicting types for '_pthread_barrier_init' >>> /usr/src/lib/libpthread/../../include/pthread.h:156: error: previous declaration of '_pthread_barrier_init' was here >>> *** Error code 1 >>> >>> Those two declarations are: >>> >>> >>>> int >>>> _pthread_barrier_init(pthread_barrier_t *barrier, >>>> const pthread_barrierattr_t *attr, int count) >>>> >>>> int pthread_barrier_init(pthread_barrier_t *, >>>> const pthread_barrierattr_t *, unsigned); >>>> >>> What is odd is that I can't see how this suddenly broke. >>> >> I just applied a fix to this. I'm not sure if this will be the >> only bug you find though (I haven't had a chance to test it >> with the recent namespace.h changes). >> > > Thanks, I'll let you know. > > Kris >