Re: Newbie: ENBD on kernel 2.6?

"Peter T. Breuer" <[email protected]>
Newsgroups gmane.linux.enbd.general
Message-ID <[email protected]>
"Also sprach [email protected]:"
> It seems like the 2.6.9-1667 include files are quite different to yours. 

Don't worry about it. Just show me what you have. I doubt there are
many things different. Show me what the relevant section of yours looks
like ...

> In mine there is this __KERNEL_STRICT_NAMES which is preventing some 
> types from being defined, hence my hack.

What makes you think so? (Please don't make changes without very closely
reasoned explanations!). What do you mean exactly? What are these
types? Do you mean that there is an #ifdef protecting some definitions?
What? Where? You must be very very very very thorough and consistent
when dealing with kernel code. You cannot "try" something, and hope.

> Anyway, I continued as root from this point in the build, and it seems 

No - please do not use root. It cannot make any difference and if you
see some difference it indicates that smething is very wrong in your
development environment!

> to have completed!
> 
> What do I do now? RTFM?

Show me what is wrong, and reason with me about what you think may fix it.
I need to see.

> -Wdeclaration-after-statement   -DMODULE -I"/usr/local/downloads/nbd-2.4.32/kernel/linux-2.6.x/include" -DKBUILD_BASENAME=enbd_ioctl -DKBUILD_MODNAME=enbd_ioctl -c -o /tmp/linux-2.6.x/drivers/block/enbd/.tmp_enbd_ioctl.o /tmp/linux-2.6.x/drivers/block/enbd/enbd_ioctl.c

looks OK. But there i something very wrong if you can "fix" a
compilation problem by sitching to root! Please do not.

>   ld -m elf_i386 -r -o /tmp/linux-2.6.x/drivers/block/enbd/enbd_ioctl.ko 
 /tmp/linux-2.6.x/drivers/block/enbd/enbd_ioctl.o /tmp/linux-2.6.x/drivers/block/enbd/enbd_ioctl.mod.o

This means nothing until you are sure the build is correct.

Then we can look at anything that crops up later.

Peter
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.