Skip to contentSkip to conversation

New System call & Kernel compilation

DISCUSSION selva kumar 4 participants 4 messages Dec 17, 2004 – Dec 18, 2004

lore
Share & tools
lore
#0 lore raw

selva:
After adding a new system call, should we have to
recompile the whole kernel? can anyone help me regarding this?

Thanks
selva

__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

#1 lore raw
Quoted 4 lines · selva kumar

selva:
After adding a new system call, should we have to
recompile the whole kernel? can anyone help me regarding this?

Yes, it's expected that you rebuild the kernel (at least all affected files), then reboot that kernel to use the new syscall.

OTOH, there has been some recent email on lkml about dynamic syscalls and a way to allow them (mostly for experimental use AIUI, but if that's the case, just rebuilding and rebooting would probably do for most people).

Signature · 1 line
~Randy
#2 lore raw
In reply to selva kumar
Quoted 4 lines · selva kumar

selva:
After adding a new system call, should we have to
recompile the whole kernel? can anyone help me regarding this?

You do not need to do a 'make clean'. Simply executing make will suffer since kbuild has track of all dependencies.

Assuming 2.6 kernel!

Sam

#3 lore raw
Quoted 8 lines
Quoted 3 lines

After adding a new system call, should we have to
recompile the whole kernel? can anyone help me regarding this?

You do not need to do a 'make clean'. Simply executing make will suffer since kbuild has track of all dependencies.

Assuming 2.6 kernel!

Even in 2.4 you do not need make clean. make dep should suffice if you changed some includes.

I dislike how many FAQs and tutorials always add "do a make clean"... that requires you to recompile everything (read: may take "some time", when in practice you only need a few things (i'm speaking generally, any app is considered).

Jan Engelhardt

Signature · 1 line
ENOSPC