[Click] Using 2.6.13.2 kernel... fails at clickfs.o

[Eddie Kohler]

Hi Martin,

The 2.6.13.2 patch doesn't work so well, but recently we created a  
2.6.16.13 patch that appears to work.  Give that a try, and let us  
know how it goes?

Eddie


On May 4, 2006, at 12:31 PM, Martin Bailon wrote:

> Hello,
>
> I'm trying to compile click as a linux kernel driver using the  
> 2.6.13.2
> kernel from kernel.org.  I patched it as the INSTALL file requires  
> with no
> mention of error.  When I try to compile click using:
>
> ./configure --enable-test --enable-analysis --enable-all-elements
> -with-linux=/usr/src/linux-2.6.13.2/
> --with-linux-map=/usr/src/linux-2.6.13.2/System.map
>
> I get the following error after a couple of minutes:
>
>   CXX [M] clickfs.o
>   {standard input}: Assembler messages:
>   {standard input}:597: Error: junk at end of line, first unrecognized
>   character is `"'
>   {standard input}:598: Error: unknown pseudo-op: `.text.lock.'
>   {standard input}:651: Error: junk at end of line, first unrecognized
>   character is `"'
>   {standard input}:652: Error: unknown pseudo-op: `.text.lock.'
>   make[3]: *** [/root/click/linuxmodule/clickfs.o] Error 1
>   make[2]: *** [_module_/root/click/linuxmodule] Error 2
>   make[2]: Leaving directory `/usr/src/linux-2.6.13.2'
>   make[1]: *** [all] Error 2
>   make[1]: Leaving directory `/root/click/linuxmodule'
>   make: *** [install] Error 1
>
> Has anyone run into this problem? If so, is there a work around?   
> Btw, I
> pulled this version of click off the cvs.
>
> Thanks in advance...
>
> - Martin
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click