[Click] click packaging

Beyers Cronje bcronje at gmail.com
Sat Feb 10 15:09:39 EST 2007


Nicola,

I've had similar problems under the elements directory, ie changing
prototypes of existing functions results in undefined symbols. A 'make
clean' followed by a 'make install' always sorts this out for me.

Beyers


On 2/9/07, Nicola Arnoldi <nicola.arnoldi at dit.unitn.it> wrote:
>
> Yes, I went through the complete setup procedure.
>
> This problem happens only with one specific package (I use two).
> Anyway, the other does not point to Notifier class...
>
> I managed to move my package dir to the elements/ folder, no need for
> packages for now.
>
> I know it may result less elegant, but....works.
>
> nicola
>
> Il giorno ven, 09/02/2007 alle 08.59 -0800, Eddie Kohler ha scritto:
> > But did you 'make install' both Click and the package?  I often forget
> > to 'make install' the package, but the "click" driver will only find the
> > package's installed version.  I just verified that
> > Notifier::upstream_empty_signal() works fine in packages on Linux for
> me.
> >
> > E
> >
> >
> > Nicola Arnoldi wrote:
> > > yes. i checked out and built from the cvs this morning, in order to
> > > avoid the problems you mention...
> > >
> > > Nicola
> > >
> > > Il giorno ven, 09/02/2007 alle 08.35 -0800, Eddie Kohler ha scritto:
> > >> Hi Nicola,
> > >>
> > >> I wonder if you have done a full "make install" of Click recently,
> from
> > >> the top-level Click directory.  This installs Click's header files in
> a
> > >> place packages can find them.  My recent changes to notification
> changed
> > >> the signature of Notifier::upstream_empty_signal.  It looks like your
> > >> package was compiled with the old signature.
> > >>
> > >> If this is not the problem let me know -- there must be something
> weird
> > >> with packages and functions with default arguments.
> > >>
> > >> Eddie
> > >>
> > >>
> > >> Nicola Arnoldi wrote:
> > >>> Of course I have!
> > >>>
> > >>>
> > >>>
> > >>> Il giorno ven, 09/02/2007 alle 10.10 -0600, Paine, Thomas Asa ha
> > >>> scritto:
> > >>>> Nicola,
> > >>>>         Be sure you have "require(wing);" at the top of your config
> file.
> > >>>>
> > >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > >>>>    Thomas Paine {paineta at uwec.edu)}
> > >>>>    University of Wisconsin - Eau Claire
> > >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > >>>>
> > >>>> -----Original Message-----
> > >>>> From: click-bounces at pdos.csail.mit.edu [mailto:
> click-bounces at pdos.csail.mit.edu] On Behalf Of Nicola Arnoldi
> > >>>> Sent: Friday, February 09, 2007 9:59 AM
> > >>>> To: Mailing list Click
> > >>>> Subject: [Click] click packaging
> > >>>>
> > >>>> Hi everybody.
> > >>>> I am trying to build a new package.
> > >>>> I followed the example of 'samplepackage'.
> > >>>> Anyway, when I launch the configuration using my brand new
> elements, I encounter the following error.
> > >>>>
> > >>>> While loading package 'wing':
> > >>>>   package /usr/lib/wing.uo: undefined symbol:
> > >>>> _ZN8Notifier21upstream_empty_signalEP7ElementiP4Task
> > >>>> requirement 'wing' not available
> > >>>> <stdin>:12: unknown element class 'WRRSched'
> > >>>> <stdin>:15: unknown element class 'MyNotifierQueue'
> > >>>> <stdin>:215: unknown element class 'BlankDecap'
> > >>>>
> > >>>>
> > >>>> It seems to be a linker error...
> > >>>> However the compilation procedure has been straightforward, with no
> errors.
> > >>>>
> > >>>>
> > >>>> some infos about my system
> > >>>>> Fedora Core 6
> > >>>>> kernel 2.6.19-1.2895.fc6
> > >>>>> gcc version 4.1.1 20070105
> > >>>>> autoconf (GNU Autoconf) 2.59
> > >>>> ...
> > >>>>
> > >>>> Nicola
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>


More information about the click mailing list