Subject: Re: problems building generic -current kernel
To: None <cube@cubidou.net>
From: Lubos Vrbka <lubos.vrbka@jh-inst.cas.cz>
List: netbsd-help
Date: 09/17/2003 15:38:21
> './build.sh tools' will build the full toolchain in order to compile
> any part of the system.
this part was ok, no problems (i had only to create /usr/obj by hand - 
why doesn't the build.sh script create it itself?). i thought 
MKOBJDIRS=yes could be in mk.conf as i found on the inet, but i don't 
have mk.conf on my system yet. i know, i can create it and put this line 
in it, but where does the build process get its defaults when no mk.conf 
is present?

> './build.sh kernel=GENERIC' will build the kernel from the GENERIC
> config file found in sys/arch/${ARCH}/conf.
this causes problems. build.sh complaints about syntax errors and that 
it has compatibility options already defined. this part of config file 
causes the problems

# Compatibility options
SYNTAX ERROR	<<<<<<< GENERIC
	options         COMPAT_NOMID    # compatibility with 386BSD, BSDI, 
NetBSD 0.8,
	options         COMPAT_09       # NetBSD 0.9,
	options         COMPAT_10       # NetBSD 1.0,
	options         COMPAT_11       # NetBSD 1.1,
	options         COMPAT_12       # NetBSD 1.2,
	options         COMPAT_13       # NetBSD 1.3,
	options         COMPAT_14       # NetBSD 1.4,
	options         COMPAT_15       # NetBSD 1.5,
	options         COMPAT_16
	options         COMPAT_43       # and 4.3BSD
SYNTAX ERROR	=======
	options         COMPAT_NOMID    # NetBSD 0.8, 386BSD, and BSDI
	options         COMPAT_09       # NetBSD 0.9
	options         COMPAT_10       # NetBSD 1.0
	options         COMPAT_11       # NetBSD 1.1
	options         COMPAT_12       # NetBSD 1.2, 386BSD, and BSDI
	options         COMPAT_13       # NetBSD 1.3, 386BSD, and BSDI
	options         COMPAT_14       # NetBSD 1.4
	options         COMPAT_15       # NetBSD 1.5
	options         COMPAT_16       # NetBSD 1.6
	options         COMPAT_43       # 4.3BSD, 386BSD, and BSDI
SYNTAX ERROR	>>>>>>> 1.570
for the second occurence of each compatibility option it says
	already have options `COMPAT_xy=1'

it seems that it doesn't understand the three lines, but why? i have the 
  up-to-date toolchain built, so this shouldn't be problem.

lubos

-- 
#####################################################
Mgr. Lubos Vrbka

Center for Complex Molecular Systems and Biomolecules
J. Heyrovsky Institute of Physical Chemistry
Academy of Sciences of the Czech Republic
Prague, Czech Republic

http://www.ncbr.chemi.muni.cz/~shnek
#####################################################