public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Building 'bind 9.11.6' fails with python error
Date: Fri, 01 Mar 2019 18:28:06 +0100	[thread overview]
Message-ID: <9a7b5545-3598-01c5-7a70-a24c320a5f39@ipfire.org> (raw)

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

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***

Sorry, I'm not sure: do we need 'dnssec-keymgr'? Or should I compile
bind with '--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 tried moving 'lfsmake2 bind' behind 'lfsmake2 python' and 'lfsmake2
python3' in 'make.sh', but this didn't work.

Any hints would be appreciated.

Best,
Matthias

             reply	other threads:[~2019-03-01 17:28 UTC|newest]

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

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=9a7b5545-3598-01c5-7a70-a24c320a5f39@ipfire.org \
    --to=matthias.fischer@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