Lo, This question belongs more to the ML you can subscribe and see archives at https://mail.gna.org/listinfo/eagleusb-dev/
I've not tested cross-compilation... your router has usb to connect the fast 800 ? do you have the result of eaglediag -msc (if bash is implemented...) ? otherwise can you give lsusb ; lsmod ; lspci ; cat /proc/version and some other useful infos you can think of. @++ Ben'. aka baud123 On Mar 7 juin 2005 9:52, Jan Rous a écrit : > Hi, > I'm trying to use Sagem [EMAIL PROTECTED] ADSL modem with wl500gx router from > asus. > The latter device runs some sort of lightweight linux on mipsel > architecture. It sadly doesn't support the modem "out-of-the-box", and > when I searched for a solution I noticed your eagle-usb kernel module. > > I tried to cross-compile it, but wasn't yet successful. I'd like to ask > you wheter you or anyone around you has managed to cross-compie > eagle-usb and could provide some how-to, or it is a thing that wasn't > yet required. > > I work on Debian Sarge with 2.6.10 kernel and using gcc 3.3.5. Kernel > for target device is located in /home/jan/ipcorder/src/kernel/kernel. > Toolchain for target device is located in /opt/brcm/hndtools-mipsel-linux. > > I've run into various problems while trying to cross-compile. > > > > 1. 'CPPFLAGS=-I/opt/hndtools-mipsel-linux/include > LDFLAGS=-L/opt/hndtools-mipsel-linux/lib ./configure --host=mipsel-linux > --build=i686-pc-linux-gnu > --with-kernel-src=/home/jan/asus/src/linux/linux/' > > Completes successsfully. With just one expectable warning: > kernel-sources version is different from the current kernel. > > However it seems that it ignores usage of mipsel-linux-gcc: > > checking for mipsel-linux-gcc... no <-------------- > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... yes > checking for suffix of executables... > checking for suffix of object files... o > > > > 2. When I try to pass the correct compiler to ./configure using: > 'CC=mipsel-linux-gcc [...] ./configure [...]' > it doesn't work at all because: > > checking for mipsel-linux-gcc... mipsel-linux-gcc > checking for C compiler default output file name... configure: error: C > compiler cannot create executables > See `config.log' for more details. > > But this is logical - that compiler's output can't be run on i686 > processors. > > > > 1a-make: Using (1) and typing make is bad. It tries to compile mipsel > kernel with i386 gcc: > > In file included from Adiutil.h:49, > from eu_utils.c:27: > /home/jan/ipcorder/src/linux/linux/include/linux/kernel.h:143:2: #error > "Please fix asm/byteorder.h" > In file included from > /home/jan/ipcorder/src/linux/linux/include/linux/kernel.h:15, > from Adiutil.h:49, > from Me.c:119: > /home/jan/ipcorder/src/linux/linux/include/asm/byteorder.h:27:4: #error > "MIPS, but neither __MIPSEB__, nor __MIPSEL__???" > > > > 1b-make: Using (1) and typing 'CC=mipsel-linux-gcc make' fails very soon > with: > > mipsel-linux-gcc -DLINUX -D__KERNEL__ -DMODULE > -I/home/jan/ipcorder/src/linux/linux//include > '-DEAGLEUSBVERSION="2.1.1"' -Wall -Wstrict-prototypes > -fomit-frame-pointer -fno-strict-aliasing -pipe > -mpreferred-stack-boundary=2 -O2 -c -o eu_main.o eu_main.c > cc1: invalid option `preferred-stack-boundary=2' <----------------- > make[1]: *** [eu_main.o] Error 1 > make[1]: Leaving directory `/home/jan/src/eagle-usb-2.1.1/driver' > make: *** [build] Error 2 > > > > My conclusion is that configure script and make procedure isn't designed > for cross-compilation at all, or I must be doing something very very > wrong. Can you, please, give me any comments about this issue? > > Thank you very much for your time and help, > with regards, > Jan Rous aka ja.ro >
