Compiling Fiasco (PR#39)

[Michael Hohmuth]

(I've put your bug report into our bugs database so that I won't
forget about it.)

David Waite <mass at ufl.edu> writes:

> I have been having problems compiling Fiasco from the CVS drop I got about
> four days ago. The OSKit seems to be having problems with both the 'depend'
> files (they are actually getting some ELF binary tacked on to the end,
> although I haven't investigated why yet). Also, the gcc v2.95 has a problem
> with the assembly (reports invalid register use in the what looked to be
> linux scsi controller drivers)

This seems to be a new problem triggered by the use of Gcc 2.95.  I
currently cannot reproduce it (I'm still using older compiler versions).

> I tried to upgrade to the newest OSKit I could find, but that didn't work
> out either, because of some header files that were there before, and that
> aren't now. (Is there some Fiasco files tacked on to the OSKit? I didn't
> really think about that until now)

We made a few bug fixes to the version of the OSKit we distribute, but 
we didn't add a lot of files.  The main problem is that the OSKit's
interface has changed a lot between releases -- all include files, for 
example, moved from <flux/foo.h> to <oskit/foo.h>, and all type names
changed to names beginning with "oskit_" --, and some of the semantics 
also changed.  Porting Fiasco to the new OSKit is easy enough (I once
did this; the patch is somewhere in the l4-hackers archive), but
because we in Dresden as a group haven't changed to the new OSKit yet, 
Fiasco hasn't, either.

Possible solutions would be to fix the old OSKit to compile with Gcc
2.95, or maybe to implement some header files which emulate the old
OSKit's interface on top of the new one.

Michael
-- 
hohmuth at innocent.com, hohmuth at sax.de
http://www.sax.de/~hohmuth/