As a second test on the same machine, I found a repo which was on a
development branch at 7.1.rc0 and I pulled from trac and have started
to make that.

The one repo I had trouble (as reported) with was one of a pair I use
for the system-wide install on the machine so that I can update one
while leaving the other for users, switching symlinks when done.  (I
do this on about 6 machines, it is such fun upgrading.)   As a result,
whenever one of this pair of repos gets updated it is by 2 releases,
and the one which I was building to 7.2 had previously had 6.10.  Was
it the 6.10 - 7.1 upgrade which required rebuilding from scratch?
That could explain something.



On 19 May 2016 at 12:42, John Cremona <john.crem...@gmail.com> wrote:
> On 19 May 2016 at 12:24, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
>> On 2016-05-19 11:55, John Cremona wrote:
>>>
>>> Jeroen: I have make's 3 times so far, here is the history:
>>
>>
>> I want to see the output of "make", i.e. the part before the "The following
>> package(s) may have failed to build:" line that you quoted.
>
> OK -- is this enough?
>
> Removing old version of IPython...
> ============================================================================
> BUILDING IPYTHON
>                 python: 2.7.8 (default, May 18 2016, 14:29:28)  [GCC 4.8.4]
>               platform: linux2
>
> OPTIONAL DEPENDENCIES
>                 sphinx: 1.4.1
>               pygments: 2.1.3
>                   nose: 1.3.7
>                pexpect: 4.0.1
> Traceback (most recent call last):
>   File "setup.py", line 326, in <module>
>     check_for_dependencies()
>   File 
> "/usr/local/sage/sage-2/local/var/tmp/sage/build/ipython-2.3.0.p0/src/setupbase.py",
> line 494, in check_for_depen
> dencies
>     check_for_pyzmq()
>   File 
> "/usr/local/sage/sage-2/local/var/tmp/sage/build/ipython-2.3.0.p0/src/setupext/setupext.py",
> line 118, in check_f
> or_pyzmq
>     import zmq
>   File 
> "/usr/local/sage/sage-2/local/lib/python2.7/site-packages/zmq/__init__.py",
> line 66, in <module>
>     from zmq import backend
>   File 
> "/usr/local/sage/sage-2/local/lib/python2.7/site-packages/zmq/backend/__init__.py",
> line 40, in <module>
>     reraise(*exc_info)
>   File 
> "/usr/local/sage/sage-2/local/lib/python2.7/site-packages/zmq/backend/__init__.py",
> line 27, in <module>
>     _ns = select_backend(first)
>   File 
> "/usr/local/sage/sage-2/local/lib/python2.7/site-packages/zmq/backend/select.py",
> line 38, in select_backend
>     ns[key] = getattr(mod, key)
> AttributeError: 'module' object has no attribute 'has'
> Error installing IPython
>
> real    0m0.666s
> user    0m0.416s
> sys     0m0.255s
> ************************************************************************
> Error installing package ipython-2.3.0.p0
> ************************************************************************
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the relevant part of the log file
>   /usr/local/sage/sage-2/logs/pkgs/ipython-2.3.0.p0.log
> Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> /usr/local/sage/sage-2/local/var/tmp/sage/build/ipython-2.3.0.p0 and
> type 'make' or whatever is appropriate.
> Instead, the following commands setup all environment variables
> correctly and load a subshell for you to debug the error:
>   (cd '/usr/local/sage/sage-2/local/var/tmp/sage/build/ipython-2.3.0.p0'
> && '/usr/local/sage/sage-2/sage' --sh)
> When you are done debugging, you can type "exit" to leave the subshell.
> ************************************************************************
> make[2]: *** 
> [/usr/local/sage/sage-2/local/var/lib/sage/installed/ipython-2.3.0.p0]
> Error 1
> make[2]: Leaving directory `/usr/local/sage/sage-2/build'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/usr/local/sage/sage-2/build'
>
>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to