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

Jason Haas jjhaas at gmail.com
Fri May 12 13:46:37 EDT 2006


I just updated click from the latest CVS and tried to compile (no kernel
recompile/patch) on 2.4.27, which was working previously.  I got the same
error message as noted in the first post of this thread but with "{standard
input}" replaced with "lib/task.cc" and different line numbers.

Jason

On 5/9/06, Martin Bailon <mbailon at dsci-usa.com> wrote:
>
> Hello again,
>
> I tried the 2.6.16.13-patch with a 2.6.16.13 kernel from kernel.org and it
> fails again.  I compile click using the following:
>
> ./configure --enable-test --enable-analysis --enable-all-elements
> --with-linux=/usr/src/linux-2.6.16.13/
> --with-linux-map=/usr/src/linux-2.6.16.13/System.map
>
> ... and I receive the following error:
>
>   CXX [M] iprw.o
> In file included from /usr/src/linux-2.6.16.13//include/net/sock.h:50,
>                  from /root/click/linuxmodule/../elements/ip/iprw.cc:36:
> /usr/src/linux-2.6.16.13//include/linux/security.h: In function `dentry*
> securityfs_create_dir(const char*, dentry*)':
> /usr/src/linux-2.6.16.13//include/linux/security.h:2619: error: invalid
> conversion from `void*' to `dentry*'
> /usr/src/linux-2.6.16.13//include/linux/security.h: In function `dentry*
> securityfs_create_file(const char*, mode_t, dentry*, void*,
> file_operations*)':
> /usr/src/linux-2.6.16.13//include/linux/security.h:2628: error: invalid
> conversion from `void*' to `dentry*'
> make[3]: *** [/root/click/linuxmodule/iprw.o] Error 1
> make[2]: *** [_module_/root/click/linuxmodule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.6.16.13'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/root/click/linuxmodule'
> make: *** [install] Error 1
>
> Has anyone else encountered this?
>
> Thank you again!
>
> Martin Bailon
>
> -----Original Message-----
> From: Eddie Kohler [mailto:kohler at cs.ucla.edu]
> Sent: Monday, May 08, 2006 9:12 PM
> To: Martin Bailon
> Cc: click at amsterdam.lcs.mit.edu
> Subject: Re: [Click] Using 2.6.13.2 kernel... fails at clickfs.o
>
> 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
>
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>
>
>


More information about the click mailing list