Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!iwarp.intel.com!pcm
From: pcm@iwarp.intel.com (Phil Miller)
Newsgroups: comp.os.minix
Subject: Re: Have you ever had this problem...?
Message-ID: <1990Mar14.151243.29980@iwarp.intel.com>
Date: 14 Mar 90 15:12:43 GMT
References: <4296@hub.UUCP>
Sender: news@iwarp.intel.com
Organization: Intel iWarp, Beaverton, Oregon, USA
Lines: 67

In article <4296@hub.UUCP> mcm@peach.ucsb.edu (Marcelo C. Mourier) writes:
>Hi there!

>    I'm having some trouble completing the 1.5.0 upgrade.  I have success-
>fully upgraded the include, library, commands, and mm; however, I couldn't
>complete the upgrading of the kernel and the fs.  Maybe someone who has run
>into the same problem could give me a clue of how to solve it.  This is
>what's happening:

>When make is processing kernel/system.c cpp complains with the following me-
>ssage:

>  "system.c", line 89: fatal error -- cannot find include file "protect.h"
>  "./proc.h", line 28: } missing
>  "./proc.h", line 28: ; missing

Don't know about this one, but read on...


>However, file protect.h is indeed present and it has the correct crc.  The
>same thing happens while make is processing fs/misc.c, cpp complains with:

>  "misc.c", line 26: fatal error -- cannot find include file "super.h"
>  "./file.h", line 6: type_identifier missing
>  "./file.h", line 6: identifier missing
>  "./file.h", line 6: (warning) no semicolon after declarator
>  "./file.h", line 6: } missing
>  "./file.h", line 6: ; missing


I had this problem with misc.c, except it wasn't `file.h'.  CPP claimed it
couldn't find `super.h', even though it's in the very same directory (not
to mention the one which lives in /usr/include).


>Again, file super.h does exist and has the correct crc.  There were no such
>problems while making mm; I don't have any idea of what could possibly be
>happening...  Any suggestions..?


Yes.  In `misc.c', there are two #include's on lines 24 and 25:

#include "param.h"
#include "super.h"

Reverse them and `misc.c' will build ok.

I have NO IDEA why the files do not work as provided.  On my system, `misc.c',
`fs/super.h', and `param.h' ALL have the correct CRC's, and also the correct
protection mode (644), but only this counter-intuitive solution works.  I say
it is counter-intuitive because I find it difficult to believe that `misc.c'
would have been posted without being tested.

>Thanks a lot for your time and help.

>Marcelo - mcm@cs.ucsb.edu


Good luck,

Phil

================================================================
--
Phil Miller             iWarp Development Program
pcm@iwarp.intel.com     Intel Corporation
                        Beaverton, Oregon