From owner-freebsd-current Tue Jul 2 9:36: 2 2002 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 B1D4437B400 for ; Tue, 2 Jul 2002 09:35:59 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33DAE43E2F for ; Tue, 2 Jul 2002 09:35:59 -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 g62GZsXO019261; Tue, 2 Jul 2002 12:35:54 -0400 (EDT) Date: Tue, 2 Jul 2002 12:35:54 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: Ian Dowse , FreeBSD current users Subject: Re: KSE status report In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2 Jul 2002, Julian Elischer wrote: > Good idea. > > Unforunatly someone tried to complie a libc_r with the old queue.h and it > had the same problem (or so they said). Well, it certainly looks wrong to use TAILQ_REMOVE inside of TAILQ_FOREACH, so either libc_r should be changed or queue.h should be reverted. Also, enabling the queue macro debugging will definitely break libc_r too. > On Tue, 2 Jul 2002, Ian Dowse wrote: > > > In message , Ju > > lian Elischer writes: > > >The big problem at the moment is that something in the > > >source tree as a whole, and probably something that came in with KSE > > >is stopping us from successfully compiling a working libc_r. > > >(a bit ironic really). > > > > Is the new > > > > (elm)->field.tqe_next = (void *)-1; > > > > in TAILQ_REMOVE a likely candidate? That could easily tickle old > > bugs in other code. The libc_r code does use a lot of TAILQ macros. > > > > Ian -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message