Jeroen: I have make's 3 times so far, here is the history:

 2015  git co master
 2016  git remote -v
 2017  make
 2018  SAGE_KEEP_BUILT_SPKGS=yes make
 2019  less /usr/local/sage/sage-2/logs/pkgs/ipython-2.3.0.p0.log
 2020  scp  /usr/local/sage/sage-2/logs/pkgs/ipython-2.3.0.p0.log warwick:
 2021  gcc -v
 2022  make
 2023  ldd local/lib/python/site-packages/zmq/backend/cython/_device.so

All three make's had the same issue with ipython.  I can just make
distclean; make now, I don't mind that.

John

On 19 May 2016 at 10:12, Francois Bissey
<francois.bis...@canterbury.ac.nz> wrote:
>
>> On 19/05/2016, at 21:05, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
>>
>> On 2016-05-19 11:01, John Cremona wrote:
>>> Volker:
>>>
>>> $ ldd local/lib/python/site-packages/zmq/backend/cython/_device.so
>>>         linux-vdso.so.1 =>  (0x00007ffd293f8000)
>>>         libzmq.so.4 => /usr/local/sage/sage-2/local/lib/libzmq.so.4
>>> (0x00007fc19ff10000)
>>>         libpython2.7.so.1.0 =>
>>> /usr/local/sage/sage-2/local/lib/libpython2.7.so.1.0
>>> (0x00007fc19fb08000)
>>>         libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>> (0x00007fc19f8d0000)
>>>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc19f508000)
>>>         librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc19f300000)
>>>         libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>> (0x00007fc19eff8000)
>>>         libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>>> (0x00007fc19ede0000)
>>>         libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc19ebd8000)
>>>         libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 
>>> (0x00007fc19e9d0000)
>>>         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc19e6c8000)
>>>         /lib64/ld-linux-x86-64.so.2 (0x00007fc1a0370000)
>>>
>>>
>>> Jeroen:
>>>
>>> The following package(s) may have failed to build:
>>>
>>> package: ipython-2.3.0.p0
>>> log file: /usr/local/sage/sage-2/logs/pkgs/ipython-2.3.0.p0.log
>>> build directory:
>>> /usr/local/sage/sage-2/local/var/tmp/sage/build/ipython-2.3.0.p0
>>
>> That's strange. What happens when you run "make" again?
>>
>
> And if you still get message about ipython-2.3.0.p0 may be look
> at the content of build/pkgs/ipython/package-version.
>
>
>
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
> --
> 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