From owner-freebsd-current  Wed Jun 14 05:33:06 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA15641
          for current-outgoing; Wed, 14 Jun 1995 05:33:06 -0700
Received: from quack.kfu.com (quack.kfu.com [204.147.226.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA15628
          for <freebsd-current@FreeBSD.org>; Wed, 14 Jun 1995 05:33:02 -0700
Received: (from nsayer@localhost) by quack.kfu.com (8.6.12/8.6.12) id FAA06881 for freebsd-current@FreeBSD.org; Wed, 14 Jun 1995 05:32:53 -0700
From: Nick Sayer <nsayer@quack.kfu.com>
Message-Id: <199506141232.FAA06881@quack.kfu.com>
Subject: Re: Problems with this morning's sup
To: freebsd-current@FreeBSD.org
Date: Wed, 14 Jun 1995 05:32:52 -0700 (PDT)
In-Reply-To: <199506140604.IAA00541@uriah.heep.sax.de> from "J Wunsch" at Jun 14, 95 08:04:30 am
X-Mailer: ELM [version 2.4 PL22]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Length: 1305      
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.

-- 
Nick Sayer <nsayer@quack.kfu.com>  | 
N6QQQ @ N0ARY.#NORCAL.CA.USA.NOAM  | "pro-choice" == "pro-abortion"
+1 408 249 9630, log in as 'guest' | "pro-choice" == "anti-adoption"
URL: http://www.kfu.com/~nsayer/   |