[Click] Building click w/ new elements

[Nels Anderson]

Aloha,

Hey Eddie, thanks for the response.  I thought that might have been the problem,
except that I scoured my element and all the ifndefs were correct.  But then, at
someone else's suggestion, I checked in the local directory and there was a
different element I wrote a while ago that I wasn't even using.  Turns out that
I forgot to change the ifndefs on that one.  Changed that and everything's fine.
  How annoying...

Anyway, thanks for the help.

-Nels

Quoting Eddie Kohler <kohler at CS.UCLA.EDU>:

> Aloha Nels,
>
> I'll bet you money that you copied an element in local/ using Print as
> a model, and you forgot to change the header-protecting #ifndef symbol
> in YOURELEMENT.hh from CLICK_PRINT_HH.  As a result print.hh is not
> being correctly included.
>
> Eddie
>
> On Oct 15, 2004, at 2:47 PM, Nels Anderson wrote:
>
> > Aloha,
> >
> > I'm currently trying to get click to build with a new element I've
> > written and
> > I'm having some problems.  I configured click with the --enable-local
> > option
> > and when I try to build it, I get this as an error message:
> >
> > g++ -W -Wall -fno-exceptions -fno-rtti  -DHAVE_CONFIG_H -I../include
> > -I../include -I. -I..  -DCLICK_USERLEVEL -g -O2 -MD -c elements.cc
> > elements.cc: In function `Element* beetlemonkey(unsigned int)':
> > elements.cc:327: error: syntax error before `;' token
> > elements.cc: In function `void click_export_elements()':
> > elements.cc:664: error: `Print' undeclared (first use this function)
> > elements.cc:664: error: (Each undeclared identifier is reported only
> > once for
> > each function it appears in.)
> > elements.cc:664: error: syntax error before `::' token
> > elements.cc: In function `void click_unexport_elements()':
> > elements.cc:928: error: syntax error before `::' token
> > gmake: *** [elements.o] Error 1
> >
> > Now, this is after it compiled the element I wrote, so I don't think
> > that could
> > be the problem.  The weird thing is, all these errors refer to the
> > print
> > element.  That doesn't really make any sense, as print isn't even a
> > local
> > element.  However, the problem is related to local elements somehow,
> > as when I
> > compile click without the --enable-local option, everything works fine.
> >
> > Anyone have any idea what the problem may be and how it could be
> > resolved?
> > Thank you for any assistance,
> >
> > -Nels
> > _______________________________________________
> > click mailing list
> > click at amsterdam.lcs.mit.edu
> > https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>