Yes, I am pretty sure this is the problem too, now that you've explained it.
Here is the output of readelf:
wbhart@ASUS:~/SageMath/local/bin$ readelf -d gp | grep RPATH
0x000f (RPATH) Library rpath:
wbhart@ASUS:~$ ldd
/home/wbhart/SageMath/local/lib/python2.7/site-packages/sage/rings/complex_double.so
linux-vdso.so.1 => (0x7fffd8abf000)
libpari-gmp-2.8.so.0 =>
/home/wbhart/SageMath/local/lib/libpari-gmp-2.8.so.0 (0x7f000977d000)
libgmp.so.16 =>
On Thursday, August 4, 2016 at 5:46:04 AM UTC-7, Bill Hart wrote:
>
> In particular, the ticket says the problem was fixed 2 months ago, and I
> downloaded the tarball just yesterday.
>
Yes, but it was resolved as "wontfix", because the patch was added to a
repository that Volker keeps outside
Erik Bray wrote:
> On Wed, Aug 3, 2016 at 3:44 PM, 'Bill Hart' via sage-devel
> wrote:
>> [BIG SNIP]
>> Note that one has access to the ordinary Windows file system, which people
>> were worried about. And 'top' works. Microsoft are definitely on the right
>> track
what is the output of ldd on
/home/wbhart/SageMath/local/lib/python2.7/site-packages/sage/rings/complex_double.so
(I guess it's linked to a system library, and on your system it's a
different one...)
On Thursday, August 4, 2016 at 1:46:04 PM UTC+1, Bill Hart wrote:
>
> In particular, the
In particular, the ticket says the problem was fixed 2 months ago, and I
downloaded the tarball just yesterday.
Bill.
On Thursday, 4 August 2016 14:44:40 UTC+2, Bill Hart wrote:
>
> Thanks for the hint. Yes, I used a binary. However, I downloaded it
> freshly from the Sage website, so I would
Thanks for the hint. Yes, I used a binary. However, I downloaded it freshly
from the Sage website, so I would guess it is not hit by any old issues?
Bill.
On Wednesday, 3 August 2016 21:27:39 UTC+2, Nils Bruin wrote:
>
> On Wednesday, August 3, 2016 at 11:16:16 AM UTC-7, Bill Hart wrote:
>>
>>
I don't know. I've spoken to one expert and he thinks almost all the issues
are due to interfaces that aren't implemented by Microsoft yet. They have
an online poll where you can vote for the features you'd most like to see
them implement. Many of the items have thousands of votes, and they are
On Wed, Aug 3, 2016 at 3:44 PM, 'Bill Hart' via sage-devel
wrote:
> There are some awful issues with WSL for now. It has a stack limit of 8MB
> which means certain programs that expect a >= 16MB stack won't work. ulimit
> refuses to increase the stack size.
Thanks
Running "make" under WSL for Sage 7.2.rc2 consistently hangs for me at this
line:
checking whether rename honors trailing slash on source...
Could that be related to limits you mention or is it some other error?
On Wednesday, August 3, 2016 at 6:44:56 AM UTC-7, Bill Hart wrote:
>
> There are
On Wednesday, August 3, 2016 at 11:16:16 AM UTC-7, Bill Hart wrote:
>
> wbhart@ASUS:~/SageMath$ ./sage -gp
> gp: error while loading shared libraries: libpari-gmp-2.8.so.0: cannot
> open shared object file: No such file or directory
>
> Is this a binary distribution? There used to be a problem
On Wednesday, 3 August 2016 18:23:27 UTC+2, vdelecroix wrote:
>
> Does at least "sage -gp" work?
>
>
No.
wbhart@ASUS:~/SageMath$ ./sage -gp
gp: error while loading shared libraries: libpari-gmp-2.8.so.0: cannot open
shared object file: No such file or directory
Bill.
--
You received this
No I didn't. But I'll set it running overnight tonight.
I wonder if it is possible to actually give someone login access to my
laptop by starting the sshd or something like that.
Bill.
On Wednesday, 3 August 2016 18:23:27 UTC+2, vdelecroix wrote:
>
> Does at least "sage -gp" work?
>
> Did you
Does at least "sage -gp" work?
Did you run "make ptestlong" to launch the tests? If so there is a log
in SAGE_ROOT/logs/ptestlong.log. That would be nice to have it!
On 03/08/16 11:45, 'Bill Hart' via sage-devel wrote:
sage -t --all seems to be passing most of its tests. Any tests that
sage -t --all seems to be passing most of its tests. Any tests that require
starting pari currently don't pass.
There were also some complaints about uncommitted changes in the git tree.
Also control.py failed its test.
I managed to kill WSL (nothing to do with Sage) at the point Sage was half
There are some awful issues with WSL for now. It has a stack limit of 8MB
which means certain programs that expect a >= 16MB stack won't work.
ulimit refuses to increase the stack size.
Building things can be *incredibly* slow. Not that this shouldn't be a
major issue for now, since it is
On Wednesday, August 3, 2016 at 11:03:50 AM UTC+2, leif wrote:
>
> VulK wrote:
> > On the topic of performances I just came across this post on phoronix:
> >
> http://www.phoronix.com/scan.php?page=article=windows-10-lxcore=1
> >
> > TL;DR: benchmarks give surprisingly good performances
* leif [2016-08-03 11:03:38]:
> VulK wrote:
> > On the topic of performances I just came across this post on phoronix:
> > http://www.phoronix.com/scan.php?page=article=windows-10-lxcore=1
> >
> > TL;DR: benchmarks give surprisingly good performances provided you do not
>
VulK wrote:
> On the topic of performances I just came across this post on phoronix:
> http://www.phoronix.com/scan.php?page=article=windows-10-lxcore=1
>
> TL;DR: benchmarks give surprisingly good performances provided you do not
> access the filesystem. At the moment, while running sage could
On the topic of performances I just came across this post on phoronix:
http://www.phoronix.com/scan.php?page=article=windows-10-lxcore=1
TL;DR: benchmarks give surprisingly good performances provided you do not
access the filesystem. At the moment, while running sage could be ok, this
would make
On Wed, Jul 27, 2016 at 8:11 AM, Nicolas M. Thiery
wrote:
> On Tue, Jul 26, 2016 at 06:29:22PM +0200, Erik Bray wrote:
>> >> OS bashing will not be tolerated.
>> >
>> > But company bashing will... ;-)
>>
>> That's not really okay either--constructive criticisms are fine
On Tue, Jul 26, 2016 at 06:29:22PM +0200, Erik Bray wrote:
> >> OS bashing will not be tolerated.
> >
> > But company bashing will... ;-)
>
> That's not really okay either--constructive criticisms are fine
+1
> but you never know where your next funding source will come from...
This argument
On Tuesday, 26 July 2016 23:12:03 UTC+2, leif wrote:
> The only difference at the C level I know of is different #includes
> (maybe some OS types and functions), and the size of long on 64-bit,
> which is only 32 bits on 64-bit Windows (only long long is 64 bits
> there), with some
William Stein wrote:
> On Tue, Jul 26, 2016 at 11:39 AM, leif wrote:
>> William Stein wrote:
>>> Regarding the above discussion about speed, what combination of
>>> OS/Virtualization/Emulations/Native/etc. is actually fastest is not
>>> something that can be determined by
The MPIR code runs ok on Windows, though it is always some small factor
behind Linux (usually 15% where we've bothered to check). So far we've been
unable to superoptimise for that platform because the OS just never gets
quiet enough for the superoptimiser to work.
However, there can be other
On Tue, Jul 26, 2016 at 11:39 AM, leif wrote:
> William Stein wrote:
>> Regarding the above discussion about speed, what combination of
>> OS/Virtualization/Emulations/Native/etc. is actually fastest is not
>> something that can be determined by "pure thought", since there
William Stein wrote:
> Regarding the above discussion about speed, what combination of
> OS/Virtualization/Emulations/Native/etc. is actually fastest is not
> something that can be determined by "pure thought", since there are
> two additional factors (which I saw a lot in work of Bill Hart, Jason
On Tue, Jul 26, 2016 at 9:37 AM, Erik Bray wrote:
> On Tue, Jul 26, 2016 at 6:33 PM, William Stein wrote:
>> On Tue, Jul 26, 2016 at 9:21 AM, leif wrote:
OS bashing will not be tolerated.
>>>
>>> But company bashing will... ;-)
On Tue, Jul 26, 2016 at 6:33 PM, William Stein wrote:
> On Tue, Jul 26, 2016 at 9:21 AM, leif wrote:
>>> OS bashing will not be tolerated.
>>
>> But company bashing will... ;-)
>>
>> Microsoft used to have a POSIX layer also; no idea what happened to that
On Tue, Jul 26, 2016 at 9:21 AM, leif wrote:
>> OS bashing will not be tolerated.
>
> But company bashing will... ;-)
>
> Microsoft used to have a POSIX layer also; no idea what happened to that
> (and how usable it actually was/is).
>
> But it never made it into mainstream
On Tue, Jul 26, 2016 at 6:21 PM, leif wrote:
> Erik Bray wrote:
>> On Tue, Jul 26, 2016 at 4:25 PM, Vincent Delecroix
>> <20100.delecr...@gmail.com> wrote:
>>>
>>>
>>> On 26/07/16 07:52, Volker Braun wrote:
On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray
Erik Bray wrote:
> On Tue, Jul 26, 2016 at 4:25 PM, Vincent Delecroix
> <20100.delecr...@gmail.com> wrote:
>>
>>
>> On 26/07/16 07:52, Volker Braun wrote:
>>>
>>> On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray wrote:
2) Currently this feature is intended as a developer
Jori Mäntysalo wrote:
> On Tue, 26 Jul 2016, VulK wrote:
>
>> Clearly performance are not going to be good, native applications are
>> the way to go for this; on the other hand I am not sure it is much (or
>> at all?) slower than a virtual machine setup.
>
> Virtualization is not emulation.
33 matches
Mail list logo