Re: OSKit mach w/St Pats

[Joachim Nilsson]

Michal 'hramrach' Suchanek wrote:

> On Thu, Jun 06, 2002 at 08:05:32AM -0700, Jeff Bailey wrote:
>  
>
> > On Thu, Jun 06, 2002 at 10:40:46AM -0400, Derek L Davies wrote:
> >
> > The tricky part is the `make' line, without which you have an
> > Oskit-mach with no drivers.  Currently I use ``make
> > kernel-ide+ethernet_vortex+ethernet_lance+ethernet_ne2000'' which
> > covers all I need on my machine and those of my friends.
> This does not work for me with current gnumach from CVS. It first 
> compiles something (dependencies?) and then complains it does not 
> know how to make the kernel-ide+ethernet_something thingie.
> Just make complains it does not know how to make kernel.
> set -e; gcc -O  -DOSKIT_MACH=1 -DMACH -DMACH_KERNEL -DKERNEL -DCONTINUATIONS 
> -DHAVE_CONFIG_H -D__ELF__=1 -Di386=1 -DAT386=1 -I./i386/i386at -I./i386/i386 
> -I./i386/include -I./i386/include/mach/sa -I./i386/bogus -I./i386 -I. -I. 
> -I./include -I./bogus -I./kern -I./device -M ./vm/vm_fault.c | sed > 
> vm_fault.d.new -e 's/vm_fault\.o:/vm_fault.o vm_fault.d:/'
> mv -f vm_fault.d.new vm_fault.d
> make: *** No rule to make target 
> `kernel-ide+ethernet_vortex+ethernet_lance+ethernet_ne2000'.  Stop.
> hramrach@hurd:/mnt/disk/src/hurd/gnumach-build$ make
> make: *** No rule to make target `kernel', needed by `all'.  Stop.

I haven't followed your pursuit this far, but how did you build the OSKit?

The modules.x86.pc file in the top directory of that package controls 
what modules are included. If you don't have the line "linux/dev" 
uncommented none of the Linux drivers will be neither built nor 
installed. On top of that you need to have a couple of environment 
variables set to build Mach correctly. Below is a snippet from a script 
I use:

MIG=/usr/bin/i386-gnu-mig           \
                                   \
CFLAGS="-g -O1"                     \
OSKIT_LIBDIR=/usr/local/lib/oskit   \
                                   \
../configure --prefix=/gnu          \
            --enable-debug         \
&& make kernel-ide+ethernet_rtl8139 \
&& sudo make install                \
&& sudo gzip -f /gnu/boot/oskit-mach

The -g flag in CFLAGS is to include debugging information (not sure of 
the effect of --enable-debug, but I use it just in case). The -O1 is to 
make sure the inline marked code in the OSKit actually get inlined, 
otherwise you'll get complaints from the compiler that it cannot find 
the cli() function.

The OSKIT_LIBDIR is where you installed the OSKit. I work with 
/usr/local for my builds, but the Debian OSKit package use 
OSKIT_LIBDIR=/usr/lib/oskit.


Hope this helps!
/Joachim

--
Joachim Nilsson /\ <http://vmlinux.org/joachim/>
Codito ergo sum \/ <joachim.nilsson@vmlinux.org>