| 1 |
If you checked that boost-build will ever only use what is currently |
| 2 |
explicitely specified: fine for me. |
| 3 |
|
| 4 |
What I don't want is: |
| 5 |
* boost using something in /usr/local |
| 6 |
* boost using something in some other location should it somehow fail to |
| 7 |
find our python (yes: I want to it to bail out) |
| 8 |
|
| 9 |
Am Freitag, den 14.12.2012, 23:08 +0100 schrieb Michał Górny: |
| 10 |
> The bootstrap script uses the sole version as well, and boost finds |
| 11 |
> the includes and libraries just fine. |
| 12 |
> --- |
| 13 |
> gx86/dev-libs/boost/boost-1.52.0-r5.ebuild | 2 +- |
| 14 |
> 1 file changed, 1 insertion(+), 1 deletion(-) |
| 15 |
> |
| 16 |
> diff --git a/gx86/dev-libs/boost/boost-1.52.0-r5.ebuild b/gx86/dev-libs/boost/boost-1.52.0-r5.ebuild |
| 17 |
> index 8659246..4f20fdf 100644 |
| 18 |
> --- a/gx86/dev-libs/boost/boost-1.52.0-r5.ebuild |
| 19 |
> +++ b/gx86/dev-libs/boost/boost-1.52.0-r5.ebuild |
| 20 |
> @@ -50,7 +50,7 @@ create_user-config.jam() { |
| 21 |
> fi |
| 22 |
> |
| 23 |
> if use python; then |
| 24 |
> - python_configuration="using python : $(python_get_version) : /usr : $(python_get_includedir) : /usr/$(get_libdir) ;" |
| 25 |
> + python_configuration="using python : $(python_get_version) ;" |
| 26 |
> fi |
| 27 |
> |
| 28 |
> cat > user-config.jam << __EOF__ |
Archives