search for: kbuild_verbose

...ecl': execl.c:(.text+0x80): undefined reference to `execve' usr/klibc/execle.o: In function `execle': execle.c:(.text+0x84): undefined reference to `execve ........ I am using gcc-4.4.3 toolchain. for kernel 2.6.31. My build command is: make CROSS_COMPILE=mipsel-linux- KLIBCARCH=mips KBUILD_VERBOSE=1 Googled around and saying that it might work if i disable distcc. So i added make CROSS_COMPILE=mipsel-linux- KLIBCARCH=mips KBUILD_VERBOSE=1 FEATURES="-distcc". But no difference. Any idea what caused this? Thanks chris -------------- next part -------------- An HTML attachment was...

...ble the NIC Gbps, through lspci, I identify the A104D. But report this error in compiling the wanpipe (./Setup install) WANPIPE DRIVER COMPILE LOG Fri Dec 22 01:19:40 BRST 2006 ----------------------------------- make -C /lib/modules/2.6.18.2-34-default/build SUBDIRS=/usr/src/wanpipe/kdrvtmp CC=gcc KBUILD_VERBOSE=0 modules make[1]: Entering directory `/usr/src/linux-2.6.18.2-34-obj/i386/default' make -C ../../../linux-2.6.18.2-34 O=../linux-2.6.18.2-34-obj/i386/default modules CC [M] /usr/src/wanpipe/kdrvtmp/sdladrv_src.o CC [M] /usr/src/wanpipe/kdrvtmp/sdladrv_fe.o /usr/src/wanpipe/kdrvtmp/sdladr...

...s/wanec/wanec.ko] undefined! CC /root/wanpipe/patches/kdrivers/wanec/wanec.mod.o LD [M] /root/wanpipe/patches/kdrivers/wanec/wanec.ko make[1]: Leaving directory `/lib/modules/2.6.10-1.771_FC2smp/build' make -C /lib/modules/2.6.10-1.771_FC2smp/build SUBDIRS=/root/wanpipe/kdrvtmp CC=gcc KBUILD_VERBOSE=0 modules make[1]: Entering directory `/lib/modules/2.6.10-1.771_FC2smp/build' CC [M] /root/wanpipe/kdrvtmp/sdla_tdmv.o CC [M] /root/wanpipe/kdrvtmp/sdla_remora_tdmv.o /root/wanpipe/kdrvtmp/sdla_remora_tdmv.c: In function `wp_remora_zap_ioctl': /root/wanpipe/kdrvtmp/sdla_remora_tdmv.c...

.../usr/src/wanpipe-3.3.16/patches/kdrivers/wanec/wanec.mod.o LD [M] /usr/src/wanpipe-3.3.16/patches/kdrivers/wanec/wanec.ko make[1]: Leaving directory `/usr/src/kernels/2.6.18-128.1.6.el5-x86_64' make -C /lib/modules/2.6.18-128.1.6.el5/build SUBDIRS=/usr/src/wanpipe-3.3.16/kdrvtmp CC=gcc KBUILD_VERBOSE=0 modules make[1]: Entering directory `/usr/src/kernels/2.6.18-128.1.6.el5-x86_64' CC [M] /usr/src/wanpipe-3.3.16/kdrvtmp/sdla_tdmv.o /usr/src/wanpipe-3.3.16/kdrvtmp/sdla_tdmv.c: In function ?wp_tdmv_software_init?: /usr/src/wanpipe-3.3.16/kdrvtmp/sdla_tdmv.c:1097: error: ?struct dahdi_span?...

...rror when i installed wanpipe stable version 2.3.4-12, i also get the same error when i used wanpipe 3.1.2 WANPIPE DRIVER COMPILE LOG Thu Jul 26 21:26:33 PHT 2007 ----------------------------------- make -C /lib/modules/2.6.22.1-27.fc7/build SUBDIRS=/usr/local/src/wanpipe-2.3.4-12/kdrvtmp CC=gcc KBUILD_VERBOSE=0 modules make[1]: Entering directory `/usr/src/kernels/2.6.22.1-27.fc7-x86_64' CC [M] /usr/local/src/wanpipe-2.3.4-12/kdrvtmp/sdladrv_src.o In file included from /usr/local/src/wanpipe-2.3.4-12/kdrvtmp/sdladrv_src.c:135: include/linux/wanpipe_common.h: In function ?wan_skb_tail?: include/lin...

...ed! > CC /root/wanpipe/patches/kdrivers/wanec/wanec.mod.o > LD [M] /root/wanpipe/patches/kdrivers/wanec/wanec.ko > make[1]: Leaving directory `/lib/modules/2.6.10-1.771_FC2smp/build' > make -C /lib/modules/2.6.10-1.771_FC2smp/build SUBDIRS=/root/wanpipe/kdrvtmp > CC=gcc KBUILD_VERBOSE=0 modules > make[1]: Entering directory `/lib/modules/2.6.10-1.771_FC2smp/build' > CC [M] /root/wanpipe/kdrvtmp/sdla_tdmv.o > CC [M] /root/wanpipe/kdrvtmp/sdla_remora_tdmv.o > /root/wanpipe/kdrvtmp/sdla_remora_tdmv.c: In function `wp_remora_zap_ioctl': > /root/wanpipe/k...

...#39;t find config.h.. I found a post on an other unrelated mailing list which stated that includes/linux/config.h has been removed from 2.6.19. It also suggested replacing all references to config.h with autoconf.h make -C /lib/modules/2.6.19.1/build SUBDIRS=/usr/src/wanpipe/kdrvtmp CC=gcc KBUILD_VERBOSE=0 modules make[1]: Entering directory `/usr/src/linux-2.6.19.1' CC [M] /usr/src/wanpipe/kdrvtmp/sdladrv_src.o In file included from /usr/src/wanpipe/kdrvtmp/sdladrv_src.c:131: include/linux/wanpipe_includes.h:226:63: linux/config.h: No such file or directory make[2]: *** [/usr/src/wanpipe...

...CC /usr/src/wanpipe-3.3.16/patches/kdrivers/wanec/wanec.mod.o LD [M] /usr/src/wanpipe-3.3.16/patches/kdrivers/wanec/wanec.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-2-amd64' make -C /lib/modules/2.6.26-2-amd64/build SUBDIRS=/usr/src/wanpipe-3.3.16/kdrvtmp CC=gcc KBUILD_VERBOSE=0 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.26-2-amd64' CC [M] /usr/src/wanpipe-3.3.16/kdrvtmp/sdla_tdmv.o /usr/src/wanpipe-3.3.16/kdrvtmp/sdla_tdmv.c: In function ?wp_tdmv_software_init?: /usr/src/wanpipe-3.3.16/kdrvtmp/sdla_tdmv.c:1097: error: ?struct dahdi_span?...

...ed! > CC /root/wanpipe/patches/kdrivers/wanec/wanec.mod.o > LD [M] /root/wanpipe/patches/kdrivers/wanec/wanec.ko > make[1]: Leaving directory `/lib/modules/2.6.10-1.771_FC2smp/build' > make -C /lib/modules/2.6.10-1.771_FC2smp/build SUBDIRS=/root/wanpipe/kdrvtmp > CC=gcc KBUILD_VERBOSE=0 modules > make[1]: Entering directory `/lib/modules/2.6.10-1.771_FC2smp/build' > CC [M] /root/wanpipe/kdrvtmp/sdla_tdmv.o > CC [M] /root/wanpipe/kdrvtmp/sdla_remora_tdmv.o > /root/wanpipe/kdrvtmp/sdla_remora_tdmv.c: In function `wp_remora_zap_ioctl': > /root/wanpipe/k...

...t.cmd +# differed from actual command line. This happens when compiler +# options changes +# (5) No dir/.target.cmd file (used to store command line) +# (6) No dir/.target.cmd file and target not listed in $(targets) +# This is a good hint that there is a bug in the kbuild file +ifeq ($(KBUILD_VERBOSE),2) +why = \ + $(if $(filter $@, $(PHONY)),- due to target is PHONY, \ + $(if $(wildcard $@), \ + $(if $(strip $(any-prereq)),- due to: $(an...

Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s

Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s