Hi Claudio,
I did actually try putting my python plugin and unboundmodule.py into the
chroot, but I completely forgot that I would also need to install the rest of
python into the chroot! Haha
Serves me right for working on it until 1am when I should should have been
asleep and trying with fre
On Wed, Aug 07, 2019 at 08:44:07AM +0100, Andy Lemin wrote:
> Morning Stuart,
>
> So I’ve tested with the base build options properly, the initial errors I saw
> before have gone which is good. But I have a more fundamental issue with
> Unbound now sadly.
>
> Swig successfully built “/usr/src/u
Morning Stuart,
So I’ve tested with the base build options properly, the initial errors I saw
before have gone which is good. But I have a more fundamental issue with
Unbound now sadly.
Swig successfully built “/usr/src/unbound/pythonmod/unboundmodule.py” and
installed it to “/usr/local/lib/py
Hi Stuart,
Thanks for your reply.
So I put in some leg work to set myself up so I could build a new release base
system, and went digging.
And I found “/usr/src/usr.src/unbound/Makefile.bsd-wrapper” so I think I have
found the correct build options to match with the base builds
CONFIGURE_OPTS
On 2019-08-06, Andy Lemin 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 Open
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-pythonmodul
6 matches
Mail list logo
