[gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[v_2e]

  Hello!
  I tried to upgrade to Sage-5.7, but could not do it because of the
following error:

>>> Compiling source
>>> in /var/tmp/portage/sci-mathematics/sage-clib-5.7/work/sage-5.7/c_lib ...
scons -j2
/usr/bin/scons: no supported Python implementation variant found!


  Regards,
    Vladimir

----- 
 <v_2e@ukr.net>

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[Christopher Schwan]

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

On Wednesday 27 February 2013 15:00:42 v_2e@ukr.net wrote:
>   Hello!
>   I tried to upgrade to Sage-5.7, but could not do it because of the
> 
> following error:
> >>> Compiling source
> >>> in /var/tmp/portage/sci-mathematics/sage-clib-5.7/work/sage-5.7/c_lib
> >>> ...
> 
> scons -j2
> /usr/bin/scons: no supported Python implementation variant found!
> 
> 
>   Regards,
>     Vladimir
> 
> -----
>  <v_2e@ukr.net>

Do you have python-2.7 properly eselected? Are PYTHON_COMPAT and USE_PYTHON 
correctly set?

Cheers,
Christopher

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

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[v_2e]

On Wed, 27 Feb 2013 14:05:55 +0100
Christopher Schwan <cschwan@students.uni-mainz.de> wrote:
> 
> Do you have python-2.7 properly eselected? Are PYTHON_COMPAT and
> USE_PYTHON correctly set?
> 
  Yes, python-2.7 is eselected, but I do not know what are
PYTHON_COMPAT and USE_PYTHON , and where can I check them.

  Regars,
    Vladimir

----- 
 <v_2e@ukr.net>

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[Francois Bissey]

On 28/02/13 21:13, v_2e@ukr.net wrote:
>   Hello!
> 
> On Thu, 28 Feb 2013 10:09:12 +1300
> fbissey@slingshot.co.nz wrote:
>>
>> Christopher meant PYTHON_TARGETS and USE_PYTHON. They are the
>> variables in /etc/make.conf (and its newer replacement
>> in /etc/portage/) that determine which python(s) you are using. The
>> first one is consumed by ebuilds using the new python-r1 eclass
>> (sage-5.7 is one), the second one is used by ebuilds using the old
>> python eclass. So Christopher's remark is that you should have at
>> least PYTHON_TARGETS="python2_7"
>> in make.conf.
>>
>   I tried it with 
>     PYTHON_TARGETS="python3_2 python2_7"
> in /etc/portage/make.conf, but it fails just in exactly the same way as
> before (without this line in config file). 
>   And also I noticed that despite I had no such line in this file
> before, all other packages detected my Python versions automatically
> during install. Why isn't it the case with Sage?
> 
OK, can we have the full build log please?

Francois

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[v_2e]

On Thu, 28 Feb 2013 21:40:44 +1300
Francois Bissey <fbissey@slingshot.co.nz> wrote:

> OK, can we have the full build log please?
> 
  Sure, but I'm afraid, there is not much information in the log.
  http://bpaste.net/show/80436/

  I'd like also to note that when I do not have the PYTHON_TARGETS
variable set in my '/etc/portage/make.conf' file, I got the following
output of 'emerge':

[ebuild     U  ] sci-mathematics/sage-clib-5.7::sage-on-gentoo
[5.6::sage-on-gentoo] 0 kB

[ebuild     U  ] sci-mathematics/sage-5.7-r1::sage-on-gentoo
[5.6::sage-on-gentoo] USE="latex -testsuite (-numpy17%
*)"PYTHON_TARGETS="python2_7" 0 kB

which means that emerge detected my version of Python correctly. But
what is it missing in such case?

  Regards,
    Vladimir

----- 
 <v_2e@ukr.net>

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[fbissey]

Quoting v_2e@ukr.net:

> On Thu, 28 Feb 2013 21:40:44 +1300
> Francois Bissey <fbissey@slingshot.co.nz> wrote:
>
>> OK, can we have the full build log please?
>>
>   Sure, but I'm afraid, there is not much information in the log.
>   http://bpaste.net/show/80436/
>
>   I'd like also to note that when I do not have the PYTHON_TARGETS
> variable set in my '/etc/portage/make.conf' file, I got the following
> output of 'emerge':
>
> [ebuild     U  ] sci-mathematics/sage-clib-5.7::sage-on-gentoo
> [5.6::sage-on-gentoo] 0 kB
>
> [ebuild     U  ] sci-mathematics/sage-5.7-r1::sage-on-gentoo
> [5.6::sage-on-gentoo] USE="latex -testsuite (-numpy17%
> *)"PYTHON_TARGETS="python2_7" 0 kB
>
> which means that emerge detected my version of Python correctly. But
> what is it missing in such case?
>
I have a nagging suspicion that scons itself is not feeling well. But 
let's try
to get more info. Do
emerge -debug -v --nodeps =sci-mathematics/sage-clib-5.7

And let's see the output of that.

Francois

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[v_2e]

  Hello!

On Fri, 01 Mar 2013 14:38:04 +1300
fbissey@slingshot.co.nz wrote:

> I have a nagging suspicion that scons itself is not feeling well. But 
> let's try to get more info. Do
> emerge -debug -v --nodeps =sci-mathematics/sage-clib-5.7
> 
> And let's see the output of that.
> 
  Here is the log: http://bpaste.net/show/80641/

  Regards,
    Vladimir


----- 
 <v_2e@ukr.net>

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[Francois Bissey]

On 01/03/13 21:43, v_2e@ukr.net wrote:
>   Hello!
> 
> On Fri, 01 Mar 2013 14:38:04 +1300
> fbissey@slingshot.co.nz wrote:
> 
>> I have a nagging suspicion that scons itself is not feeling well. But 
>> let's try to get more info. Do
>> emerge -debug -v --nodeps =sci-mathematics/sage-clib-5.7
>>
>> And let's see the output of that.
>>
>   Here is the log: http://bpaste.net/show/80641/
> 

I was hoping there would be interesting stuff.
Does scons work? What does
scons -v
do?

If you go in the ebuild directory
/var/tmp/portage/sci-mathematics/sage-clib-5.7/work/sage-5.7/c_lib
and run scons manually there, what happens?

Francois

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[v_2e]

On Fri, 01 Mar 2013 22:57:16 +1300
Francois Bissey <fbissey@slingshot.co.nz> wrote:
> 
> I was hoping there would be interesting stuff.
> Does scons work? What does
> scons -v
> do?
> 
> If you go in the ebuild directory
> /var/tmp/portage/sci-mathematics/sage-clib-5.7/work/sage-5.7/c_lib
> and run scons manually there, what happens?
> 
  Well, absolutely the same thing happens:

# scons -v
/usr/bin/scons: no supported Python implementation variant found!


    Vladimir

----- 
 <v_2e@ukr.net>

Re: [gentoo-science] [sage-on-gentoo] sage-clib-5.7 fails to build

[Francois Bissey]

On 01/03/13 23:32, v_2e@ukr.net wrote:
> On Fri, 01 Mar 2013 22:57:16 +1300
> Francois Bissey <fbissey@slingshot.co.nz> wrote:
>>
>> I was hoping there would be interesting stuff.
>> Does scons work? What does
>> scons -v
>> do?
>>
>> If you go in the ebuild directory
>> /var/tmp/portage/sci-mathematics/sage-clib-5.7/work/sage-5.7/c_lib
>> and run scons manually there, what happens?
>>
>   Well, absolutely the same thing happens:
> 
> # scons -v
> /usr/bin/scons: no supported Python implementation variant found!
> 

Your scons is definitely broken. First step would be trying to
re-install it.

Francois

[gentoo-science] Re: [sage-on-gentoo] sympy-0.7.2-r2 fails to build

[v_2e]

  Hello!
  After re-emerging 'scons' and updating both portage and
'sage-on-gentoo' overlay, I do not observe build problems with
sage-clib any more, but now sympy fails to build.
  Here is the build log: http://bpaste.net/show/81612/

  Regards,
    Vladimir

----- 
 <v_2e@ukr.net>

Re: [gentoo-science] Re: [sage-on-gentoo] sympy-0.7.2-r2 fails to build

[fbissey]

Quoting v_2e@ukr.net:

>   Hello!
>   After re-emerging 'scons' and updating both portage and
> 'sage-on-gentoo' overlay, I do not observe build problems with
> sage-clib any more, but now sympy fails to build.
>   Here is the build log: http://bpaste.net/show/81612/
>
Sorry Vladimir, I got buried in stuff. Can you please uninstall gmpy?
At least set MPMATH_NOGMPY=1 before emerging sympy.

We should just ask everyone who uses sage-on-gentoo to mask gmpy.

If you install sage, mpmath and therefore sympy won't work with gmpy. 
Don't even
try. mpmath will install normally but not sympy because it import itself at
compilation/install time. You can shutdown the use of gmpy in mpmath by 
setting
MPMATH_NOGMPY. There is similarly a MPMATH_NOSAGE variable but it is broken in
that one sage import is not under its control.

Upstream mpmath knows about the last problem. Not sure when there will be a
release to fix it.

Francois

Re: [gentoo-science] Re: [sage-on-gentoo] sympy-0.7.2-r2 fails to build

[v_2e]

  Hello!

On Fri, 08 Mar 2013 09:46:08 +1300
fbissey@slingshot.co.nz wrote:

> Sorry Vladimir, I got buried in stuff. Can you please uninstall gmpy?
> At least set MPMATH_NOGMPY=1 before emerging sympy.
> 
  I uninstalled gmpy, but I still get an error:

 AttributeError: 'module' object has no attribute 'ipapi'

  Full log: http://bpaste.net/show/82199/

    Vladimir

----- 
 <v_2e@ukr.net>

Re: [gentoo-science] Re: [sage-on-gentoo] sympy-0.7.2-r2 fails to build

[Francois Bissey]

On 08/03/13 20:08, v_2e@ukr.net wrote:
>   Hello!
> 
> On Fri, 08 Mar 2013 09:46:08 +1300
> fbissey@slingshot.co.nz wrote:
> 
>> Sorry Vladimir, I got buried in stuff. Can you please uninstall gmpy?
>> At least set MPMATH_NOGMPY=1 before emerging sympy.
>>
>   I uninstalled gmpy, but I still get an error:
> 
>  AttributeError: 'module' object has no attribute 'ipapi'
> 
>   Full log: http://bpaste.net/show/82199/

That would be related to ipython from the log I can that this
ipython interaction is coming through sage being called from mpmath
itself called from sympy.

Considering that sage 5.7 has switched to ipython 0.13.1 that your sage
install is not completely consistent/complete. Do you have
sage-baselayout at 5.7 and sage itself at 5.6? If that's the case one
way out would be to unmerge sage, upgrade sympy, and then merge sage
again. There are other ways but that's a bit more complicated.

Francois

Re: [gentoo-science] Re: [sage-on-gentoo] sympy-0.7.2-r2 fails to build

[v_2e]

  Hello!

On Fri, 08 Mar 2013 20:53:07 +1300
Francois Bissey <fbissey@slingshot.co.nz> wrote:
> 
> Considering that sage 5.7 has switched to ipython 0.13.1 that your
> sage install is not completely consistent/complete. Do you have
> sage-baselayout at 5.7 and sage itself at 5.6? If that's the case one
> way out would be to unmerge sage, upgrade sympy, and then merge sage
> again. There are other ways but that's a bit more complicated.
> 
  Yes, that indeed was the case. So I unmerged Sage and then merged the
new one (5.7) which depends on sympy. So, now everything seems to work
fine.
    Thanks!

    Vladimir

----- 
 <v_2e@ukr.net>