From owner-freebsd-i386@FreeBSD.ORG  Tue May  4 15:35:02 2004
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
Delivered-To: freebsd-i386@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id EFED116A4CF; Tue,  4 May 2004 15:35:02 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C0CCF43D39; Tue,  4 May 2004 15:35:02 -0700 (PDT)
	(envelope-from simon@FreeBSD.org)
Received: from freefall.freebsd.org (simon@localhost [127.0.0.1])
	i44MZ2OO032475;	Tue, 4 May 2004 15:35:02 -0700 (PDT)
	(envelope-from simon@freefall.freebsd.org)
Received: (from simon@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i44MZ2fu032471;
	Tue, 4 May 2004 15:35:02 -0700 (PDT)
	(envelope-from simon)
Date: Tue, 4 May 2004 15:35:02 -0700 (PDT)
From: "Simon L. Nielsen" <simon@FreeBSD.org>
Message-Id: <200405042235.i44MZ2fu032471@freefall.freebsd.org>
To: phil.addy@bradford.gov.uk, simon@FreeBSD.org,
	freebsd-i386@FreeBSD.org
Subject: Re: i386/60249: Undefined reference to arp_ifinit while linking
	kernel
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 May 2004 22:35:03 -0000

Synopsis: Undefined reference to arp_ifinit while linking kernel

State-Changed-From-To: open->closed
State-Changed-By: simon
State-Changed-When: Tue May 4 15:34:57 PDT 2004
State-Changed-Why: 
Build errors should be posted to either the freebsd-questions or the
freebsd-stable mailing lists rather than filing a PR.

Also, to debug a problem like this you need to supply your complete
kernel configuration file since that is most likely where the problem
is.

It might also be a good idea to update to a more recent FreeBSD
version if possible - not that 4.7 should be broken, it's just easier
for people to help find your problem when you run the same version
they do.

http://www.freebsd.org/cgi/query-pr.cgi?pr=60249