Re: Couple of questions

(This email started out in another direction when I realized that i 
hadn't tested it with specifing the LINUXDIR on the make line after I 
got it to work with the 2.6.11.6 kernel...however, such a small thing I 
thought I would make note of it for anyone else that might have the same 
issues)

Ok....

So, I d/l 2.6.11, 2.6.11.6 and 2.6.12.3 kernel sources, and did a make 
modules; make bzImage on each so that a) I know that the kernel builds 
ok and b) necessary things are made.

Also I noticed on your reply that it built fine with 2.6.11.6 and that 
you were using nbd-2.4.32, so I d/l enbd-2.4.32pre.tgz

tar xvfz enbd-2.4.32pre.tgz
make LINUXDIR=/usr/src/linux-2.6.11.6
-- everything works fine.

in fact even with linux-2.6.12.3, everything works find as long as I use:
make LINUXDIR=/usr/src/linux-2.6.12.3

however, even if I ln -s /usr/src/linux-2.6.12.3 -> /usr/src/linux and 
just run make I get all sorts of errors like :

In file included from 
/lib/modules/2.6.9-11.ELsmp/build/include/asm/byteorder.h:31,
                  from 
/lib/modules/2.6.9-11.ELsmp/build/include/linux/cdrom.h:14,
                  from /var/tmp/nbd-2.4.32/nbd/ioctl.c:59:
/lib/modules/2.6.9-11.ELsmp/build/include/linux/byteorder/little_endian.h:43: 
error: syntax error before "__cpu_to_le64p"


Which I notice it goes to /lib/modules... for some of the includes if 
LINUXDIR isn't specified on the make line, and is specified in the 
Makefile as /usr/src/linux. This is probably what the web page was 
talking about, but it wasn't clear to me and I thought that it warranted 
noting.

Long story short:
Compiled fine for both 2.6.11.6 and 2.6.12.3

Thanks,
B

Peter T. Breuer wrote:
> "Also sprach Robert Scussel:"
> 
>>I have vanilla 2.6.11 kernel code and am trying to get enbd working with 
>>that.  I notice that when I run the make it says to use the patch to the 
>>source
> 
> 
> No it DOESN'T - that's for starters. Just run make. Show me any ęrrors
> you get and I'll diagnose. DOn't complicate - it's perfectly easy.
> 
> 
> 
>>but I can't seem to find a patch for the 2.6.11 code, which 
> 
> 
> There are plenty of patches and any reasonable one will work. The only
> thing you are patching is the kernel config files! But just run "make".
> 
> Peter


-- 
Robert Scussel
1024D/BAF70959/0036 B19E 86CE 181D 0912  5FCC 92D8 1EA1 BAF7 0959