From owner-freebsd-current Sun Oct 1 12:22:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id DA96C37B503; Sun, 1 Oct 2000 12:22:39 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91JMNU53246; Sun, 1 Oct 2000 12:22:24 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Mike Smith Cc: Michael Harnois , current@FreeBSD.ORG Subject: Re: Today -current broken on build In-Reply-To: Message from Mike Smith of "Sun, 01 Oct 2000 12:14:25 PDT." <200010011914.e91JEPh03548@mass.osd.bsdi.com> Date: Sun, 01 Oct 2000 12:22:23 -0700 Message-ID: <53242.970428143@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. It wasn't clear to me if it was clashing with the internal typedef or something else - the namespace issues with gcc are a little unclear to me here (at least it's not VMS C, with a global member name space :). In any case, we can certainly revert the change if it transpires that the pollution came from elsewhere and for now, at least, -current is working again. clock.c includes a butt-load of system headers through am_defs.h and I can't immediately tell if the callout stuff is being exposed inappropriately or not. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message