NetBSD Problem Report #32714

From  Fri Feb  3 03:00:08 2006
Return-Path: <>
Received: by (Postfix, from userid 1358)
	id E517563B86B; Fri,  3 Feb 2006 03:00:07 +0000 (UTC)
Message-Id: <>
Date: Fri,  3 Feb 2006 03:00:07 +0000 (UTC)
Subject: config(1)(9) doesn't know about prerequisites
X-Send-Pr-Version: 3.95

>Number:         32714
>Category:       bin
>Synopsis:       config(1)(9) doesn't know about prerequisites
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 03 03:05:01 +0000 2006
>Last-Modified:  Sat Jun 24 08:40:54 +0000 2006
>Originator:     Rui Paulo
>Release:        NetBSD 3.99.15

System: NetBSD 3.99.15 NetBSD 3.99.15 (QUARK) #43: Sun Jan 29 03:22:38 WET 2006 i386
Architecture: i386
Machine: i386

Some of our drivers/subsystems have prequisistes that config should know
about. config should have a way to specify what requires what and then
automagically include the dependencies or warn the user.

Let's see, for example, the stf problem:
defpseudo stf:          ifnet
file    net/if_stf.c                    stf & inet & inet6      needs-flag

If one builds a kernel with stf but without inet6, the build will
fail becaause stfattach() is automatically included in ioconf.c b
config(1). This is not being idiot-proof. (how may times did you tried
building a kernel without mpacpi/mpbios but with ioapic?)



config couuld have the following require directive:

	require stf:	inet & inet6
	require ioapic: mpbios | mpacpi



Responsible-Changed-From-To: gnats-admin->kern-bug-people
Responsible-Changed-When: Sat, 24 Jun 2006 08:40:54 +0000

reassigned to proper default responsible party.


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.