From owner-freebsd-current Wed Jun 14 13:23:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA28073 for current-outgoing; Wed, 14 Jun 1995 13:23:44 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA28067 for ; Wed, 14 Jun 1995 13:23:39 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA01696; Wed, 14 Jun 1995 13:23:18 -0700 From: "Rodney W. Grimes" Message-Id: <199506142023.NAA01696@gndrsh.aac.dev.com> Subject: Re: Problems with this morning's sup To: nsayer@quack.kfu.com (Nick Sayer) Date: Wed, 14 Jun 1995 13:23:18 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199506141232.FAA06881@quack.kfu.com> from "Nick Sayer" at Jun 14, 95 05:32:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1652 Sender: current-owner@FreeBSD.org Precedence: bulk > > J Wunsch writes: > > > As Nick Sayer wrote: > > > > > > 2. After fixing that, a make world gets as far as half way through > > > building libc, whereupon it crashes with this little bit of noise: > > > /usr/src/lib/libc/net/ether_addr.c:80: dereferencing pointer to incomplete type > > > /usr/src/lib/libc/net/ether_addr.c: In function `ether_aton': > > > /usr/src/lib/libc/net/ether_addr.c:92: storage size of `o' isn't known > > > /usr/src/lib/libc/net/ether_addr.c: In function `ether_ntoa': > > > > If anayone has any ideas, I'd love to hear them. If this was something > > > warned of in current, then I'm sorry but I've only recently > > > resubscribed. > > > Nope, Garrett didn't warn on -current. I've only seen his commits of > > the new mrouting code. Looks like you first need to perform a ``cd > > /usr/src/include; make install'' before compiling the lib. ``make > > world'' is supposed to always do it in the correct sequence, but it's > > rather overkill. > > Humph. Is there a way to sup 2.0.5-RELEASE? If not, is there a way > to fix this? :-) I know I could ftp 2.0.5-RELEASE, but sup is more > convenient. There is not, and probably never will be a way to sup frozen releases, the best we can do is what I am working on now, and that is setting up the -stable set of sup targets. At this very moment that tree is almost 2.0.5 (it is 2.0.5R merged into the HEAD of the main cvs branch so the only difference is RCS ID strings.) This will become the 2.1 release. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD