>> dpc.h is the first file in the build that tries to access the kernel headers - the errors shows it is trying to find these headers in the target fs, rather than from the kernel install. Can you double check that the BASE_BUIDOS is set correctly to point to your kernel headers?
~roger -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren J Longhorn Sent: 28 March 2007 19:03 To: [email protected] Subject: Re: Building dsplink Monk, Roger wrote: > 3. modify make/Linux/davinci_mvlpro4.0.mk to configure your BASE_BUIDOS > to point to your linux kernel and the arm tools specific paths > accordingly (BASE_OSINC, OSINC_PLATFORM, OSINC_TARGET, BASE_OSLIB). Thanks for the pointers Roger, I have set up these as follows: BASE_BUILDOS := $(MY_CONFIGURED_KERNEL) BASE_CGTOOLS := /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin BASE_OSINC := $(BASE_BUILDOS)/include OSINC_GENERIC := $(BASE_OSINC) OSINC_PLATFORM := /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/lib/gcc/armv5tl-montavi sta-linuxeabi/3.4.3/include OSINC_TARGET := /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/include When I build I get errors : Compiling dpc.c... In file included from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/linux/sched.h:4, from dpc.c:19: /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/param.h:14:61: asm/arch/param.h: No such file or directory In file included from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/page.h:27, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/cpu-single.h:33, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/proc-fns.h:154, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/system.h:95, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/bitops.h:22, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/linux/bitops.h:77, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/linux/thread_info.h:20, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/linux/spinlock.h:12, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/linux/capability.h:45, from /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/linux/sched.h:7, from dpc.c:19: /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/../target/usr/inclu de/asm/glue.h:111:2: #error Unknown data abort handler type There's more, but that's where it starts to go wrong. I'm guessing that either OSINC_PLATFORM, OSINC_TARGET, or both need tro point somewhere else, but I'm not sure where? Cheers Darren _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
