public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Building 'bind 9.11.6' fails with python error
Date: Sat, 02 Mar 2019 16:51:25 +0000	[thread overview]
Message-ID: <42A58B10-5A0F-4D17-B72A-EDE999492576@ipfire.org> (raw)
In-Reply-To: <ca67e225-b2c3-43aa-122b-43eef4327372@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2643 bytes --]

Hi,

I have never heard of “ply” before, but it is a lever for Python.

However, it does not matter because we don’t need it anyways…

-Michael

> On 1 Mar 2019, at 19:45, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> On 01.03.2019 18:31, Michael Tremer wrote:
>> Hi,
>> 
>>> On 1 Mar 2019, at 17:28, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>> 
>>> Hi,
>>> 
>>> Building current 'bind 9.11.6' suddenly fails with the following errors:
>>> 
>>> ***SNIP***
>>> checking for perl... /usr/bin/perl
>>> checking for python... no
>>> checking for python3... no
>>> checking for python3.7... no
>>> checking for python3.6... no
>>> checking for python3.5... no
>>> checking for python3.4... no
>>> checking for python3.3... no
>>> checking for python3.2... no
>>> checking for python2... no
>>> checking for python2.7... no
>>> checking for Python support... no
>>> configure: error: Python required for dnssec-keymgr
>>> make: *** [bind:76: /usr/src/log/bind-9.11.6] Error 1
>>> ***SNAP***
>> 
>> We have python 2.7 which should be found here. Probably bind is built before Python is built?
> 
> It is. I tried building it *after* Python, but: see below.
> 
>> Have a look in config.log what went wrong during detection...
> 
> ***SNIP***
> ...
> checking for python2... /usr/bin/python2
> checking if /usr/bin/python2 is python2 version >= 2.7 or python3
> version >= 3.2... yes
> checking Python module 'argparse'... yes
> checking Python module 'ply'... no
> checking for python2.7... /usr/bin/python2.7
> checking if /usr/bin/python2.7 is python2 version >= 2.7 or python3
> version >= 3.2... yes
> checking Python module 'argparse'... yes
> checking Python module 'ply'... no
> checking for Python support... no
> configure: error: Python required for dnssec-keymgr
> make: *** [bind:76: /usr/src/log/bind-9.11.6] Error 1
> ...
> ***SNAP***
> 
> What is meant with "module 'ply'"? I can't find it.
> 
>>> Sorry, I'm not sure: do we need 'dnssec-keymgr'? Or should I compile
>>> bind with '--without-python’?
>> 
>> No, we do not need that tool. We don’t use bind to sign any DNSSEC zones.
> 
> Ok. Adding '--without-python'.
> 
>>> Excerpt from 'configure'-help:
>>> "# Python is also optional but required by default so that dnssec-keymgr
>>> # gets installed unless explicitly prevented by the user using
>>> # --without-python.”
>> 
>> I guess disabling works.
> 
> Yes. It does:
> 
> ***SNIP***
> ...
> checking for Python support... disabled
> ...
> ***SNAP***
> 
> ;-)
> 
> Best,
> Matthias


      reply	other threads:[~2019-03-02 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 17:28 Matthias Fischer
2019-03-01 17:31 ` Michael Tremer
2019-03-01 19:45   ` Matthias Fischer
2019-03-02 16:51     ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42A58B10-5A0F-4D17-B72A-EDE999492576@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox