From owner-freebsd-current Thu May 28 13:02:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11928 for freebsd-current-outgoing; Thu, 28 May 1998 13:02:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11910 for ; Thu, 28 May 1998 13:02:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00920; Thu, 28 May 1998 11:56:54 -0700 (PDT) Message-Id: <199805281856.LAA00920@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: Argh! errno spam! In-reply-to: Your message of "Thu, 28 May 1998 11:35:33 +1000." <199805280135.LAA00604@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 11:56:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >There are a few perfectly good reasons to call a structure member errno, > >but regardless of the good reasons, I fear for the code in the ports > >collection. 8( > > I'd like the ports collection to be compiled routinely under -current. > Even if it doesn't compile, the breakage list would be interesting. You can either do this yourself, or request that a volunteer do it for you. Bento is equipped to build ports under -current, and you should have no access problems. > >I was bitten by this with the NetBSD-derived bootcode I'm working on, > >which doesn't use libc and thus needs its own errno in order to be a > >reasonable facsimile therof. (Yes, I have a workaround.) > > errno shouldn't be defined for non-libc interfaces. You probably got > bitten by namespace pollution. KERNEL must be defined to stop errno > being defined in our errno.h. Actually, the NetBSD code was written to think it was "like" the kernel, so it includes . We define the errno macro there, not in . Defining KERNEL resolves the issue for this application at least. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message