1 |
On Thu, 05 Dec 2013 13:32:09 +0900 |
2 |
heroxbd@g.o wrote: |
3 |
|
4 |
> Dear all, |
5 |
> |
6 |
> I have only one python-2.7 on my system. Simple and stupid. |
7 |
> |
8 |
> After boost ebuild is converted to python-r1, libboost_python.so is |
9 |
> renamed to libboost_python-2.7.so. This is all cool about python-r1 |
10 |
> for multiple python implementation support. |
11 |
> |
12 |
> At the same time, I don't need this feature. I have a couple of |
13 |
> Jamroot's which append "-lboost_python" to LDFLAGS, and I have to |
14 |
> manually specify "-lboost_python-2.7". Moreover, libraries depending |
15 |
> on boost.python, e.g. Boost.NumPy[1], searches for boost_python and |
16 |
> boost_python-mt only. I am forced to patch the build system to pass |
17 |
> "-${PYVAR}" to it, which is tedious. |
18 |
|
19 |
Shouldn't pkg-conifg --libs handle this? |
20 |
|
21 |
> I am looking for a way out. Candidates are, |
22 |
> |
23 |
> 1. scan all python versioned libraries and symlink them to |
24 |
> unversioned one. Question: hints to do it systematically in |
25 |
> portage? Is there a helper available like python-exec? |
26 |
> |
27 |
> 2. python-single-r1 is ready for use, but it requires manipulating |
28 |
> the boost ebuild to change from python-r1, if I want a |
29 |
> python-single-r1 blessed boost. Question: How about merging |
30 |
> python-single-r1 with python-r1 and controlling by a global USE |
31 |
> flag "python-single". When "python-single" is set, all ebuilds |
32 |
> inheriting python-r1 behaves as if being with python-single-r1, |
33 |
> so that all python versionings on executables and libraries are |
34 |
> disabled. |
35 |
> |
36 |
> 3. or something I missed |
37 |
> |
38 |
> Comments? |
39 |
> |
40 |
> Benda |
41 |
> |
42 |
> 1. https://github.com/ndarray/Boost.NumPy |
43 |
> |
44 |
|
45 |
|
46 |
|
47 |
--- |
48 |
Jan Matějka | Gentoo Developer |
49 |
https://gentoo.org | Gentoo Linux |
50 |
GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B |