[Click] click-devirtualize and kernel 2.6

[Giovanni Di Stasi]

Il Thursday 07 February 2008 19:27:57 hai scritto:
> Hi Eddie,
>
> Just did a test on one of my own elements and I've run into some errors
> again. Are there any recommendations or "gotchas" to know of when coding a
> custom element in order for click-devirtualize to support it?
>
> Here is the error I get:
>
> [root at slacker click]# click-devirtualize -f conf/le1000.click | click
> While loading package 'clickdv_t_2COpEyFhZH8rwZZl3u6c':
>   /usr/local/bin/click-buildtool makepackage -q -C /tmp/clicktmp30201/ -t
> userlevel  -w -fno-access-control  clickdv_t_2COpEyFhZH8rwZZl3u6c
> clickdv_t_2COpEyFhZH8rwZZl3u6c.u.cc 1>&2
>   CXX clickdv_t_2COpEyFhZH8rwZZl3u6c.u.cc
> clickdv_t_2COpEyFhZH8rwZZl3u6c.u.cc: In member function 'Packet*
> UDevE1000_a_afd::input_pull(int) const':
> clickdv_t_2COpEyFhZH8rwZZl3u6c.u.cc:111: error: 'i' was not declared in
> this scope
> make[1]: *** [clickdv_t_2COpEyFhZH8rwZZl3u6c.u.uo] Error 1
>
>
> Here is the section in the output file that click-devirtualize generates
> that obviously causes the error:
>
> inline Packet *
> UDevE1000_a_afd::input_pull(int) const
> {
>   return input(i).pull();
> }
>
>
> If I just manually change to UDevE1000_a_afd::input_pull(int i) I get
> further, but then it spews out a whole list of other errors, so I'm not
> sure what the ramifications are by manually changing the output file of
> click-devirtualize.
>

I did an analougous test and I can confirm the same behaviour with my 
configuration.




      ___________________________________ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html