Re: Kernel Compilation problem - Partially Solved

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 15, 2002 at 02:38:49PM -0500, Narasimhamurthy Giridhar wrote:
> But I did get it working. I am just not sure if its the right way of doing
> it. I changed /usr/include/asm/unistd.h by adding #define __NR_mycall 191
> to it . I have made similar change in /usr/src/linux/include/asm/unistd.h
> also.
> 
> Is this good, safe etc. ???

No. You are _still_ using /usr/include/asm/unistd.h. Kernel modules do
not use /usr/include/. Never. (I'd be willing to argue that any modules
that *are* using /usr/include/ are vastly broken, no matter if they work
or not.)

Yes, it is a pain in the arse to get these things setup. An important
pain in the arse, so it is worth your time reading and re-reading all
available documentation about this until you understand it. :)

If you are on a debian system, apt-get install kernel-package, and go
read /usr/share/doc/kernel-package/*eader* -- that is one of the most
comprehensive documents I have seen on the matter. If you aren't on a
debian system, it is worth your time to manually extract the file from
whatever debian has easily available through their website. :)

And, the kernelnewbies.org FAQ has this documented -- read, and re-read,
until it makes sense. It will. It just takes time. :)

Cheers :)

-- 
http://immunix.org/

Attachment: pgp00047.pgp
Description: PGP signature


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux