module building
[email protected] Mon, 14 Apr 2003 04:30:53 -0700
| Newsgroups | gmane.comp.handhelds.zaurus.devel |
|---|---|
| Message-ID | <FC0B9DA2600ED4118F76009027AA5DDD05EF9320@ALEX2> |
Hi, I am trying to build my own module that will be dynamically loaded onto the Zaurus at the IPv6 level to obtain some data for my application. I have set up my build environment as suggested in the http://docs.zaurus.com/linux_compiler_setup_howto.shtml site and tested this. I also know this works because I was able to build kernel and the IPv6 stuff as a module and load it onto the Zaurus. This quite happily now interacts with my IPv6 test network. Typically on a standard Linux platform my Makefile to build my module looks like this: CC=gcc MODCFLAGS= -I/lib/modules/2.4.17/build/include -Wall -DMODULE -D__KERNEL__ -02 -DLINUX my.o: my.c $(CC) $(MODCFLAGS) -c $< I have tried various things for the MODCFLAGS include directive but nothing seems to work. The CC line has been changed to CC=$(TMAKEPATH) to pick up the environment settings for cross compilation. Obviously, the -I/lib ... stuff in the above line is incorrect, but what should it be set too for cross compilation? Can anyone help? Thanks in advance, Francisco ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf