public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Dave Reisner <d@falconindy.com>
Cc: util-linux@vger.kernel.org
Subject: Re: building pylibmount when python -> python3
Date: Mon, 26 Aug 2013 12:43:51 -0400	[thread overview]
Message-ID: <201308261243.52183.vapier@gentoo.org> (raw)
In-Reply-To: <20130826124730.GN699@rampage>

[-- Attachment #1: Type: Text/Plain, Size: 1104 bytes --]

On Monday 26 August 2013 08:47:30 Dave Reisner wrote:
> This came up in IRC and I thought it might be a good idea to mention it
> to the list. With pylibmount recently being merged into git, some folks
> might have trouble building from HEAD if their /usr/bin/python points to
> a version python>=3.0. While the end goal (after discussion with Karel)
> seems to be that we should be able to build this for both python2 and
> python3, you can work around the build failure for now by simply passing
> --with-python=/usr/bin/python2 (or --without-python if you don't care
> for the new module).

that doesn't quite work due to logic in the configure script that rejects 
anything other than "yes".  fixing that doesn't help as AM_PATH_PYTHON only 
respects $PYTHON.  then you have to set it to the full path and not just 
PYTHON=python2 because the configure script wants the full path (to run the 
config script).  it's all pretty fragile atm.

i think the workaround is:
	$ PYTHON=/usr/bin/python2 ./configure
(or point it at python2.7 if your distro installs a fuller version)
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-26 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 12:47 building pylibmount when python -> python3 Dave Reisner
2013-08-26 16:43 ` Mike Frysinger [this message]
2013-08-26 16:52   ` Dave Reisner

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=201308261243.52183.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=d@falconindy.com \
    --cc=util-linux@vger.kernel.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