search for: kerneldir

On Thu, Apr 12, 2012 at 03:48:29PM +0800, 15102925731 wrote: > BTW, the Makefile is as folllow, > > CC := gcc > obj-m := hellomodule.o > KERNELDIR := /lib/modules/`uname -r`/build > PWD := $(shell pwd) > modules: > $(MAKE) -C $(KERNELDIR) M=$(PWD) modules ^^^^^^^^^^^^^^ Check the Makefile under KERNELDIR directory. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Ac...

Sorry, but I didn't find a Makefile under KERNELDIR. Why is it necessary to check that makefile anyway??? As to the Makefile that I posted before, if I can changed that file to build the .c into .bc rather then .o, that would also solve my problem! Thank you! -- 祝好！ 甄凯 --------------------------------------------------------------...

BTW, the Makefile is as folllow, CC := gcc obj-m := hellomodule.o KERNELDIR := /lib/modules/`uname -r`/build PWD := $(shell pwd) modules: $(MAKE) -C $(KERNELDIR) M=$(PWD) modules Can I use an option of clang to specify the KERNELDIR ,etc? Thank you! -- 祝好！ 甄凯 -------------------------------------------------------------------------------------------...

I may try to use the Makefile then. When using gcc the Makefile is CC := colorgcc obj-m := hello.o KERNELDIR := /lib/modules/2.6.36.1/build PWD := $(shell pwd) modules: $(MAKE) -C $(KERNELDIR) M=$(PWD) modules #modules install: # $(MAKE) -C $(KERNELDIR) M=$(PWD) modules_install How to change it so the generating result is .bc file not the .o file? PLEASE BE KIND AND HELP ME~~ -- 祝好！...

...new kernel files given below, I can not compile the new driver anymore. kernel-headers-2.6.18-164.9.1.el5 kernel-PAE-devel-2.6.18-164.9.1.el5 kernel-PAE-2.6.18-164.9.1.el5 The make command can not find /include/linux/version.h file with the following error. But the file is already there. make KERNELDIR= /lib/modules/2.6.18-164.9.1.el5PAE/build grep: /include/linux/version.h: No such file or directory expr: syntax error ../../../inc/linux/Makefile.def:85: *** Only kernel 2.4/2.6 is supported but you use 2.. Stop. [root at server linux]#locate include\/linux\/version.h command gives the followi...

Wow that's to much output information. Maybe I can put it in this way. Could you tell me the clang option that can include the linux kernel headers??? Something like "clang -O3 -isystem /lib/modules/`uname -r`/build/include -emit-llvm hellomodule.c -c -o hellomodule.bc" Thank you! -- 祝好！ 甄凯

Using the new method for building a standalone kernel module (although seems to happen with the traditional way as well) I get "mach_mpspec.h: No such file or directory" Same result if I try to do a kernel 'make'. Subsequently I get MAX_MP_BUSSES and MAX_IRQ_SOURCES undeclared. This should surely work 'out of the box' with Centos ? Any ideas about what's missing ?

Dear Chen, I tried the command you told me. It turns out that clang use -I option rather then -isystem. But after I included the init.h file, it fired at me that "asm/processor.h" is not fount. Then I included that file using -I option and some other files were said not found! It's like I opened a can of worms... I can still continue to include the file that is said not found. But

In order to build a kernel module outside of a kernel source tree, I understand it is necessary to set up a makefile containing lines such as ... obj-m:=driver.o ... and quote the KERNELDIR directory to the make system (e.g. see O'Reilly book on Linux device drivers) However, doing this with Centos either 'as-is', or even after doing a yum remove kernel-devel-<version> then yum upgrade kernel-devel, (to cause a reinstall of the latest version) leads to a series of...

Thanks for your help and patience! Best regards, Zhen Kai At 2012-04-16 15:35:25,"陳韋任" <chenwj at iis.sinica.edu.tw> wrote: >> The thing is that I know the Makefile to complete that task. But what I want to know the clang command that can do that. Since the makefile will generate a .ko file while I can use the clang command "-O3-emit-llvm" to generate a

I used the following command to solvee the missing kernel problem. ./configure --with-port=0x3f8 --with-irq=4 --with-transmitter --enable-sandboxed --with-driver=serial --with-kerneldir=/lib/modules/2.6.9-11.EL/build Things are going much better now.. Jerry ---------- Karanbir, I am still having problems. I grabbed the rpm and installed it. I could not get a /dev/lircd device. I put the lirc.rules in /etc/udev/... even rebooted and still not there. I then grabbed the src rp...

...==================| 9.8 kB 00:00 update : ################################################## 28/28 Added 12 new packages, deleted 0 old in 0.15 seconds Parsing package install arguments No Match for argument: kernel-sourcecode Nothing to do I tried using /usr/src/kernels/2.6.9-22.EL-i686 as KERNELDIR but that doesn't work. I tried "yum search /usr/src/linux" and "yum provides /usr/src/linux" with no result. I installed everything from the 4 centOS CD's but none of the scsi.h located on the system looks like the one I need as they don't define `SCSI_DISK0_MAJOR&...

...ratch/trees/ocfs2-1.2/configure.in 2007-03-27 16:22:52.000000000 -0400 +++ ocfs2-1.2.5.devel/configure.in 2007-04-15 17:13:49.000000000 -0400 @@ -108,13 +108,14 @@ AC_ARG_WITH(kernel-source, [ --with-ker AC_MSG_RESULT($kernelsourcedir) KERNELSRC="$kernelsourcedir" +KERNELBUILD="$kerneldir" KERNELINC="$KERNELSRC/include" - -if test ! -f "$KERNELINC/linux/autoconf.h"; then +if test ! -f "$KERNELBUILD/include/linux/autoconf.h"; then AC_MSG_ERROR(No configured kernel include tree found) fi - -OCFS2_CHECK_KVER($KERNELINC, ksourceversion, "...

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

...Configure for full emulation as: > ./configure --target-list=ppc64-softmmu --enable-attr > > Configure for power-kvm as: > ./configure --enable-kvm --target-list=ppc64-softmmu --enable-fdt \ > --cc="gcc -m64" \ > --kerneldir=/root/kheaders --enable-io-thread --enable-attr > > Note: --enable-attr is required for 9p support. On ppc64 systems, libattr > should be compiled and installed manually as it is not distributes in > 64bit packages. Before including such a patch, we should really discuss the desired i...

...Configure for full emulation as: > ./configure --target-list=ppc64-softmmu --enable-attr > > Configure for power-kvm as: > ./configure --enable-kvm --target-list=ppc64-softmmu --enable-fdt \ > --cc="gcc -m64" \ > --kerneldir=/root/kheaders --enable-io-thread --enable-attr > > Note: --enable-attr is required for 9p support. On ppc64 systems, libattr > should be compiled and installed manually as it is not distributes in > 64bit packages. Before including such a patch, we should really discuss the desired i...

This two-part patch for supermin implements device trees (for ARM). The first patch introduces a more rational way to handle command line arguments in 'supermin-helper'. See the commit message for details. The old style is still supported for compatibility. The second patch adds an extra supermin-helper --dtb parameter specifying a wildcard. A device tree file which matches the

Hi, I''ve been using btrfs for my root partition for about a month on archlinux and recently Ive started using the i3 window manager and starting X manually and I now boot to run level 3 (multi-user.target for systemd) and Ive noticed that booting archlinux on a btrfs root, there is a lot off hdd chatter after the login prompts are displayed, which doesnt happen with ext4 on root, so I

...t; - -#include "error.h" -#include "xvasprintf.h" -#include "full-write.h" - -#include "helper.h" - -#ifndef O_CLOEXEC -#define O_CLOEXEC 0 -#endif - -/* Directory containing candidate kernels. We could make this - * configurable at some point. - */ -#define KERNELDIR "/boot" -#define MODULESDIR "/lib/modules" - -static char* get_kernel_version (char* filename); -static const char *create_kernel_from_env (const char *hostcpu, const char *kernel, const char *kernel_env, const char *modpath_env, const char *dtb_wildcard, const char *dtb); -stat...