I've wanted to try to use python & boost for a while, but their tutorial depends on using bjam, which has been a pain to try and figure out. And of course the boost-python developers think that jam is the best thing ever and don't bother providing any documentation of how to use boost-python in a more traditional environment.

Here's my stab.

/* hello.cxx */
#include <boost/python.hpp>
using namespace boost::python;

char const* greet()
{
  return "hello, world";
}

BOOST_PYTHON_MODULE(hello)
{
  def("greet", greet);
}

I compiled it on an amd64 linux box with the following.

$ g++ -c -fpic -I/usr/include/python2.3 hello.cxx -o hello.o
$ g++ -shared -fpic -lpython2.3 -lboost_python hello.o -o hello.so
$ python
>>> import hello
>>> print hello.greet()

It turns out the -fpic is required for the AMD64 box, and on an x86 box, is unnecessary. (Though it doesn't hurt to have leave it in).

Would it have been too hard to show the manual way before extolling the virtues of their build system? Perhaps they were just being lazy as coming up with a simple build script on windows would probably be a lot harder than the above.

I was looking at the log files and discovered that pidentd was throwing error messages about netlink_lookup: write failed: Connection refused

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305926

Seems to suggest that adding the module should make it shut up.

So I added the following to /etc/modules # tcp_diag may shut pidentd up about netlink_lookup: write failed tcp_diag