Sascha, Sascha Alexander Jopen wrote: > Ok, thats bad news. > But what is the problem in supporting 2.6.25? > The problems i described are not kernel but configure script related. > And if there are kernel problems, too, maybe i could solve them. The > only patch part i couldn't apply so far, was one with an error message > regarding preemption in spinlock_types.h, but that should have no > functional consequences. > So why is the kernel mode not supported?
I think Yongheng misspoke; if a patch applies, then that's not the problem. I suspect the problem is something that Harald Schiöberg mentioned years ago, namely that you have supplied a CXXFLAGS argument for the target compiler, but Click's configure scripts are passing those arguments to the *build* compiler, which doesn't recognize them. This is a stupid problem and I don't know the right way to fix it long term. (Any bright ideas, anyone?) But a workaround is to not set CXXFLAGS. Instead set CXX, to something like CXX="name-of-your-compiler CXXFLAGS". Eddie > Regards, > Sascha > > Yongheng Qi schrieb: >> click kernel mode not supprt 2.6.25. >> >> 2009/5/22 Sascha Alexander Jopen <[email protected]>: >>> Hello, >>> >>> i'm trying to crosscompile click with its linux kernel module. I would >>> like to compile for mips for OpenWrt 8.09 with kernel 2.6.25. I patched >>> the kernel and compiled it sucessfully. >>> Configuring click for crosscompiling fails, however. config.log reports >>> the following errors: >>> cc1plus: error: unrecognized command line option "-m64" >>> cc1plus: error: unrecognized command line option "-mno-red-zone" >>> cc1plus: error: unrecognized command line option "-mcmodel=kernel" >>> cc1plus: error: unrecognized command line option >>> "-maccumulate-outgoing-args" >>> >>> These errors occur, because the configure script passes options to the >>> mipsel compiler, which are legal for i386-compilers only. I pass --host >>> --build and --target options to the script for mipsel-linux and >>> i486-linux-gnu respectively. Configuring for userlevel driver works >>> without problems. >>> >>> So my question is: What do i have to do, to make configure use the >>> correct compiler flags for the target system, not the build system? >>> >>> Thanks in advance, >>> Sascha >>> _______________________________________________ >>> click mailing list >>> [email protected] >>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click >>> >> >> > > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
