Hi! I apologize if this has been brought up already, haven't had time to read up on the latest threads.
While building Suricata against the latest PF_RING svn i noticed that ./configure failed due to undefined references to numa functions. I'm guessing this will be seen in other 3rd party apps being built against PF_RING svn as well. I use Debian Wheezy and I believe it's related to the "recent" DSO Linking changes. I think this applies to later Ubuntu editions too. While I do know some programming, I'm not a programmer by profession or so, so I can't suggest the proper action here. But I think this link below might give you some hints to maybe change how linking against numa is done: https://wiki.debian.org/ToolChain/DSOLinking I've brought this up on the OISF-devel mailing list too: https://lists.openinfosecfoundation.org/pipermail/oisf-devel/2014-February/002970.html At the moment, the solutions is to pass -lnuma via LIBS when running ./configure Maybe the PF_RING Suricata guide (and other guides for 3rd party applications) can be changed to reflect this. At least those utilizing the PF_RING svn. The following section at http://www.ntop.org/pf_ring/accelerating-suricata-with-pf_ring-dna/ --- Compile and install ./autogen.sh && LIBS=-lrt ./configure --enable-pfring ... --- Should be changed to: --- Compile and install ./autogen.sh && LIBS="-lrt -lnuma" ./configure --enable-pfring ... --- Regards, Johan Karlsson _______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
