From: yac <yac@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] python versioned libraries or not
Date: Sat, 7 Dec 2013 23:34:14 +0100 [thread overview]
Message-ID: <20131207233414.18be7ef6@gentoo.org> (raw)
In-Reply-To: <86eh5rx6ie.fsf@moguhome00.in.awa.tohoku.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]
On Thu, 05 Dec 2013 13:32:09 +0900
heroxbd@gentoo.org wrote:
> Dear all,
>
> I have only one python-2.7 on my system. Simple and stupid.
>
> After boost ebuild is converted to python-r1, libboost_python.so is
> renamed to libboost_python-2.7.so. This is all cool about python-r1
> for multiple python implementation support.
>
> At the same time, I don't need this feature. I have a couple of
> Jamroot's which append "-lboost_python" to LDFLAGS, and I have to
> manually specify "-lboost_python-2.7". Moreover, libraries depending
> on boost.python, e.g. Boost.NumPy[1], searches for boost_python and
> boost_python-mt only. I am forced to patch the build system to pass
> "-${PYVAR}" to it, which is tedious.
Shouldn't pkg-conifg --libs handle this?
> I am looking for a way out. Candidates are,
>
> 1. scan all python versioned libraries and symlink them to
> unversioned one. Question: hints to do it systematically in
> portage? Is there a helper available like python-exec?
>
> 2. python-single-r1 is ready for use, but it requires manipulating
> the boost ebuild to change from python-r1, if I want a
> python-single-r1 blessed boost. Question: How about merging
> python-single-r1 with python-r1 and controlling by a global USE
> flag "python-single". When "python-single" is set, all ebuilds
> inheriting python-r1 behaves as if being with python-single-r1,
> so that all python versionings on executables and libraries are
> disabled.
>
> 3. or something I missed
>
> Comments?
>
> Benda
>
> 1. https://github.com/ndarray/Boost.NumPy
>
---
Jan Matějka | Gentoo Developer
https://gentoo.org | Gentoo Linux
GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-12-07 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 4:32 [gentoo-dev] python versioned libraries or not heroxbd
2013-12-07 22:34 ` yac [this message]
2013-12-07 23:44 ` heroxbd
2013-12-09 21:27 ` Luca Barbato
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=20131207233414.18be7ef6@gentoo.org \
--to=yac@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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