On 2019-08-06, Andy Lemin <andrew.le...@gmail.com> wrote: > Hi guys, > > I’m just after some general advice as I feel like I’m doing something wrong, > and having to hack around too much for what I believe should be simple. > > I am developing a simple Python plugin for Unbound, and the default Unbound > install on OpenBSD sadly wasn’t built with “—with-pythonmodule”. > > So I grabbed the Unbound source code with a git clone from GitHub, installed > dependencies, and did “./configure —with-pythonmodule”, make, make install > etc.. > > So nothing special here. It installed to /usr/local/ rather than just /usr > etc, and so fiddled around with /etc/rc.d/unbound to make the rc scripts > start the custom one. > > But I’m getting errors which requires some extra config settings to squash > when loading the same config as with the built in Unbound. ok maybe newer > unbound code.. > > But I am then also getting errors when trying to load the stock example > python plugin as per the source built sphinx docs. > > I’m not at my computer at the moment so can’t share the exact errors, but > thought I’d ask as it feels like I’m missing something obvious! > > Maybe I need some extra build options or static library references to make it > as smooth as the built in Unbound? Or maybe I should be using a different > source? > > Any initial thoughts? I’ll post exact errors as soon as I can.
Initial thoughts are "did you use the same configure flags as much as possible as the build in base". Really need to see the errors to be able to make any more detailed suggestions. The default install can't include Python support, because the default install of Unbound is in the base OS, and Python isn't.
