Subject: Re: Current csc.o wanted!
To: Markus Baeurle <emw4maba@gp.fht-esslingen.de>
From: Chris Gilbert <cg110@york.ac.uk>
List: port-arm32
Date: 11/06/1997 10:13:42
Morning Markus,

On Wed, 5 Nov 1997, Markus Baeurle wrote:

> Hi Mark,
> 
> thanks for providing the csc.o.
> But I can't get the kernel to compile, I get an error in
> .../arm32/arm32/disassem.h when trying to compile disassem.c. It is
> something like "argument format specified for non-function" which is
> reported for the last pointer to a function in the only struct in this
> headerfile. 

Sounds like a macro is wrong somewhere...

> I have no clue what this is about, as there are similar definitions like
> this which don't give an error.
> I should mention that I'm using GCC as supplied with 1.2-R but this
> shouldn't be the problem. I'm not so sure about the headerfiles in
> /usr/include/machine and /usr/include/sys though, maybe I should replace
> them with the sup'ed ones from /usr/src/sys....? I have already copied a
> few of them but I'm not sure if it's the right thing to replace them all.

/usr/include/machine and /usr/include/sys should be one of two things:

i) copies of directories found within /usr/src/sys, if you've still got
the ones from the gcc set then you definetly need to delete them and copy
them from the relevent directories.  If I remember typing make includes in
the /usr/src/sys directory does this for you by default, (although there
was a bug in one of the arch/arm32 Makefiles that made it go wrong, can't
remember what, something to do with a line needing to be commented out,
I'll take a look later today, it may have been fixed by now.)

ii) make sym-links to the relevant directory, this method has the
advantage that you don't have to copy the header files every time you
sup.  This can also be done by make includes if you've set something in a
.mk file somewhere.

Another thing to check is that you've got the latest make and config
executables, and that you've also got the latest .mk files, they're in
src/share/mk I think, oh and make a backup of the old .mk files, AFAIR you
need a need to have a new make to use the new .mk's and to make the new
make you need the old make and the old .mk files (I hope that's not too
confusing...)

Sorry this is a bit unclear, but it's been a while (3 months) since I last
did a kernel compile and things may have changed since then so the above
could all be wrong (and probably is ;)

Cheers,
Chris