Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Sep 1997 07:45:13 +0930
From:      Greg Lehey <grog@lemis.com>
To:        "Raymond (Arden Computers)" <raymond@ardennet.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: problem in building custom kernel
Message-ID:  <19970919074513.31715@lemis.com>
In-Reply-To: <3.0.3.32.19970918142054.032f9484@mail.ardennet.com>; from Raymond (Arden Computers) on Thu, Sep 18, 1997 at 02:20:54PM -0700
References:  <3.0.3.32.19970918142054.032f9484@mail.ardennet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 18, 1997 at 02:20:54PM -0700, Raymond (Arden Computers) wrote:
> At 12:13 PM 9/17/97 +0930, you wrote:
>> On Tue, Sep 16, 1997 at 06:54:59PM -0700, Arden Computers NetServices wrote:
>>> Hi there,
>>>
>>> I keep having problems in building my KERNEL.  I have followed the
>>> instruction on the HANDBOOK to build a customized KERNEL.  It is running on
>>> an Intel Pentium 100 system with 32MB Ram.  One IDE hard drive and one IDE
>>> CD-ROM.  There are no EISA nor the SCSI system insides.  I have attached my
>>> Kernel BEE2 in here.  As for trouble shooting purpose, this Kernel is
>>> similar to GENERIC with only a few critical settings being modified.
>>>
>>> I have no problem doing the .../config BEE2 and .../make depend
>>> But when I run the make from /usr/src/compile/BEE2, it has the following
>>> errors:
>>> DFFS -DINET -KERNEL  ../../kern/kern_clock.c
>>> ../../kern/kern_clock.c:937: malformatted character constant
>>> ../../kern/kern_clock.c:937: parse error before character constant
>>> ../../kern/kern_clock.c:86: warning: `initclocks' declared `static' but
>>> never defined
>>> *** Error code 1
>>
>> You don't say how you got the sources, or what version this is
>> supposed to be.  I've just checked the source of
>> /sys/kern/kern_clock.c (the -current version, RCS ID $Id:
>> kern_clock.c,v 1.40 1997/09/07 05:25:43 bde Exp $) and find no
>> constants round there.  I'd guess that you have a corrupted source
>> file.  Take a look round line 937.  You should see something like:
> ==========================================
> The FreeBSD I got is installed through FTP server at ftp.freebsd.com.  I
> installed the FreeBSD last week.  I have checked the kern_clock.c, the
> version is.....
>
> kern_clock.c,v 1.28.2.1 1997/02/04 21:03:43 jhay Exp $
>
> Then, I went to line 937, and I the source code I have was same as what you
> have.
>>
>>
>>       if (CLKF_USERMODE(frame)) {
>>		p = curproc;
>>		if (p->p_flag & P_PROFIL)
>>			addupc_intr(p, CLKF_PC(frame), 1);
>>		if (--pscnt > 0)
>>			return;
>>		/*
>>		 * Came from user mode; CPU was in user state.
>>		 * If this process is being profiled record the tick.
>>		 */
>>
>> If not, let me see what it is.  Let me also see the RCS ID (should be
>> at line 39).
>>
> ======================
> Do you think I should download and install the FreeBSD again?

No.  Repeat after me:

  REINSTALLING IS THE LAST POSSIBLE RESORT, AND SELDOM SOLVES THE
  PROBLEM.

I know it's common in the Microsoft world, because people seldom have
any choice, but it's really not a good idea here.

> BTW, the current GENERIC kernel is running fine, I think may be I
> don't have to make a customized kernel.  What do you think?

I don't know what you've changed, so it's difficult to say, but there
should be no problem in building a kernel.

Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970919074513.31715>