Subject: kern/31063: config should check conflicts and dependences
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <unex@linija.org>
List: netbsd-bugs
Date: 08/25/2005 00:12:00
>Number: 31063
>Category: kern
>Synopsis: config should check conflicts and dependences
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Aug 25 00:12:00 +0000 2005
>Originator: unex@linija.org
>Release: NetBSD 2.0.2_STABLE
>Organization:
>Environment:
System: NetBSD linija.org 2.0.2_STABLE NetBSD 2.0.2_STABLE (Linija-$Revision) #0: Sun Jun 12 16:43:39 EEST 2005 root@linija.org:/usr/obj/sys/arch/i386/compile/LINIJA i386
>Description:
In NetBSD 3.0_BETA pf can't co-exist with altq, so if I'll make config with altq and pf lines, it compiles with errors like:
/usr/src/sys/dist/pf/net/pf.c: In function `pf_send_tcp':
/usr/src/sys/dist/pf/net/pf.c:1355: error: dereferencing pointer to incomplete type
Same with VERIFIED_EXEC, if I compile it with fingerprint hash (for ex. VERIFIED_EXEC_FP_RMD160), I'll get errors:
kern_verifiedexec.o(.text+0x176): In function `veriexec_init_fp_ops':
: undefined reference to `RMD160Init'
I think, config should warn about conflicts and dependences like this.
>How-To-Repeat:
Compile kernel with VERIFIED_EXEC and any fingerprint hash, but WITHOUT pseudo-device crypto, or compile pf with altq.
>Fix: