On Monday, September 2, 2013 4:19:37 AM UTC+2, nil...@gmail.com wrote:
>
>
>
>> try rebasing some more...
>>
>>
> I tried hard, no way. Even my colleagues report all the same error as the
> initiator of this theme did (no relation to). We've also tried 5.9 and
> 5.11 with 64bit Cygwin, but t
>
> try rebasing some more...
>
>
I tried hard, no way. Even my colleagues report all the same error as the
initiator of this theme did (no relation to). We've also tried 5.9 and
5.11 with 64bit Cygwin, but there are problems with mpir and ppl.
There is a portable Cygwin evolving (http://po
On 2013-08-29, nil...@gmail.com wrote:
>
>
>>Am Donnerstag, 29. August 2013 23:33:43 UTC+2 schrieb Dima Pasechnik:
>>
>>
>> >This is a typical sign that a rebase in needed.
>> >cf. http://trac.sagemath.org/ticket/14031
>>
>>
> Yes, that worked. Many thanks !
>
> Unfortunately another error occur
>Am Donnerstag, 29. August 2013 23:33:43 UTC+2 schrieb Dima Pasechnik:
>
>
> >This is a typical sign that a rebase in needed.
> >cf. http://trac.sagemath.org/ticket/14031
>
>
Yes, that worked. Many thanks !
Unfortunately another error occured, possibly caused by the same Python
issue ...
On 2013-08-29, nil...@gmail.com wrote:
>> The Python interpreter included with Cygwin executes python -c "import
>> hashlib" >without incident, while the version built with Sage prints Aborted
>> (core >dumped). However, there is no problem if the version provided by Sage
>> is run >with no arg
> The Python interpreter included with Cygwin executes python -c "import
> hashlib" >without incident, while the version built with Sage prints Aborted
> (core >dumped). However, there is no problem if the version provided by Sage
> is run >with no arguments and the line import hashlib is entere
