Subject: Re: kernel clock.c not compiling correctly for VAX410?
To: None <port-vax@netbsd.org>
From: None <jkunz@unixag-kl.fh-kl.de>
List: port-vax
Date: 02/24/2000 22:15:41
On 24 Feb, NetBSD Mailing list wrote:

> I just experienced something rather strange with clock.c and a 
> VAX41 config file kernel build:
I had the same while compiling -current from the Feb. 20 tar-files:

ld -N -Ttext 80000000 -e start -S -o netbsd ${SYSTEM_OBJ} vers.o
ka410.o: Undefined symbol `_clk_adrshift' referenced from text segment
ka410.o: Undefined symbol `_clk_tweak' referenced from text segment
ka410.o: Undefined symbol `_clk_page' referenced from text segment
ka410.o: Undefined symbol `_clk_page' referenced from text segment
ka410.o: Undefined symbol `_clk_page' referenced from text segment
ka410.o: Undefined symbol `_clk_page' referenced from text segment
ka410.o: Undefined symbol `_chip_clkread' referenced from data segment
ka410.o: Undefined symbol `_chip_clkwrite' referenced from data segment
ka43.o: Undefined symbol `_clk_adrshift' referenced from text segment
ka43.o: Undefined symbol `_clk_tweak' referenced from text segment
ka43.o: Undefined symbol `_clk_page' referenced from text segment
ka43.o: Undefined symbol `_clk_page' referenced from text segment
ka43.o: Undefined symbol `_clk_page' referenced from text segment
ka43.o: Undefined symbol `_clk_page' referenced from text segment
ka43.o: Undefined symbol `_chip_clkread' referenced from data segment
ka43.o: Undefined symbol `_chip_clkwrite' referenced from data segment
*** Error code 1

Stop.

I added options for some other VAXen and then it worked. The diff from
the configfiles:
[root@oblina src]# diff /bigtmp/oblina /usr/src/sys/arch/vax/conf/oblina        
15,17c15,17
< # options     "VAX630"        # MV II
< # options     "VAX650"        # MV III, 3600, 3800, 3900
< # options     "VAX670"        # VAX 4000/300
---
> options       "VAX630"        # MV II
> options       "VAX650"        # MV III, 3600, 3800, 3900
> options       "VAX670"        # VAX 4000/300
20,22c20,22
< # options     "VAX46"         # VS 4000/60
< # options     "VAX48"         # VS 4000 VLC
< # options     "VAX49"         # VS 4000/90
---
> options       "VAX46"         # VS 4000/60
> options       "VAX48"         # VS 4000 VLC
> options       "VAX49"         # VS 4000/90

I think there are some dependancys between the CPU-types not proper
resolved in the source. I am working to locate the error closer. 
-- 



tschüß,
         Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/