From owner-freebsd-current  Tue Jun  9 08:31:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA19340
          for freebsd-current-outgoing; Tue, 9 Jun 1998 08:31:57 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lexmark.lexmark.com (interlock2.lexmark.com [192.146.101.10])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA19297
          for <freebsd-current@freebsd.org>; Tue, 9 Jun 1998 08:31:40 -0700 (PDT)
          (envelope-from fireston@lexmark.com)
Received: by interlock2.lexmark.com id AA12348
  (InterLock SMTP Gateway 3.0 for freebsd-current@freebsd.org);
  Tue, 9 Jun 1998 11:31:22 -0400
Message-Id: <199806091531.AA12348@interlock2.lexmark.com>
Received: by interlock2.lexmark.com (Protected-side Proxy Mail Agent-1);
  Tue, 9 Jun 1998 11:31:22 -0400
From: Mik Firestone <fireston@lexmark.com>
Subject: kernel broken?
To: freebsd-current@FreeBSD.ORG (Mail list FreeBSD-current)
Date: Tue, 9 Jun 1998 11:31:20 -0400 (EDT)
Reply-To: fireston@lexmark.com
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I sup'd a new world this morning ( around 4:00 am, EDT ) and was able to build
the world with -DNOLKM.

When I went to build a new kernel, though, I received this error:
  cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Wpointer-arith
  -Winline -Wuninitialized -ansi  -nostdinc -I- -I. -I../.. -I../../../include
  -DKERNEL -include opt_global.h  ../../kern/kern_clock.c
  ../../kern/kern_clock.c: In function `microtime':
  ../../kern/kern_clock.c:517: too few arguments to function
  ../../kern/kern_clock.c: In function `nanotime':
  ../../kern/kern_clock.c:535: too few arguments to function
  ../../kern/kern_clock.c: In function `microuptime':
  ../../kern/kern_clock.c:577: too few arguments to function
  ../../kern/kern_clock.c: In function `nanouptime':
  ../../kern/kern_clock.c:593: too few arguments to function
  ../../kern/kern_clock.c: In function `init_timecounter':
  ../../kern/kern_clock.c:629: too few arguments to function
  ../../kern/kern_clock.c:643: too few arguments to function
  ../../kern/kern_clock.c:653: too few arguments to function
  ../../kern/kern_clock.c: In function `sync_other_counter':
  ../../kern/kern_clock.c:712: too few arguments to function
  ../../kern/kern_clock.c: At top level:
  ../../kern/kern_clock.c:795: warning: initialization from incompatible
  pointer type
  ../../kern/kern_clock.c:796: warning: initialization makes pointer from
  integer without a cast
  ../../kern/kern_clock.c:799: warning: initialization makes integer from
  pointer without a cast

It seems a call to get_timecount is responsible for these problems.  Each time
it is used, get_timecount is called like: tc->get_timcount().

If I have read /usr/include/sys/time.h correctly ( and no promises there ),
get_timecount is expecting a timecounter pointer in the param list.  

Before I go around randomly inserting pointers, what should the calls to
get_timecount in kern_clock actually look like?

Thanks, 
Mik
-- 
Mik Firestone fireston@lexmark.com
If ever I become an Evil Overlord:
I will not grow a goatee. In the old days they made you look diabolic.  Now
they just make you look like a disaffected member of Generation X.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message