From owner-freebsd-current Tue Jul 2 2:20:20 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 4827737B405 for ; Tue, 2 Jul 2002 02:20:14 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E09143E0A for ; Tue, 2 Jul 2002 02:20:10 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702092009.IJNV6023.sccrmhc02.attbi.com@InterJet.elischer.org> for ; Tue, 2 Jul 2002 09:20:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA95597 for ; Tue, 2 Jul 2002 02:07:07 -0700 (PDT) Date: Tue, 2 Jul 2002 02:07:07 -0700 (PDT) From: Julian Elischer To: 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 BTW feel free to spend some time helping try figire out why libc_r is bombing out. It's not an exclusive club :-) On Tue, 2 Jul 2002, Julian Elischer wrote: > > Ok so Usability for the average command line user is > very good. David Xu tracked down a problem that was > eluding me with SMP machines. Matt is tracking down > something that may be giving some instability > but may also be related to what David found. > He however gets the award for most confusing > debug messages when he managed to get both of his CPUs > to enter teh debugger at the same time. I thought that was > impossible, but it definitly happenned. (or it certainly > looked that way to me :-) > > 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). > > A libc_r imported from a system that is not yet upgraded to have > KSE sources works fine. A libc_r from a KSE machine > will not work correctly on the KSE machine or the pre-KSE machine. > > The sources are identical, so some thing else in the tree must be > influencing its correctness. > > the result of this problem is that KDE and Gnome apps that > are linked with a libc_r created on this system. > > The test directory in the libc sources is giving me some avenues to > work on but I must say, given allthe things that could have gone wrong > in the kernel, I'm surprised that the largest problem seems to > have come from a userland library that I haven't touched :-/ > > julian > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message