Il giorno venerdì 3 agosto 2012 06:57:32 UTC+2, jason ha scritto:
>
>
>
> Basically:
>
> 1. apply the patch that is failing
>
> 2. Look at the .rej files it mentions and apply the necessary changes to
> the Sage library manually.
>
> 3. sage -hg qrefresh to update the patch
>
> 4. Put the upd
> I can only confirm this fact, but this is indeed an upstream issue.
> Also, it is really a problem, does it break anything?
>
Not really, it's just that it takes more time.
The dll.a thing on Cygwin would really great to have in my opinion.
--
--
To post to this group, send an email to s
In ticket #13237, I have upgraded Singular to version 3-1-5 (with
various upstream patches). It fixes a lot of bugs in multivariate
factorization, and also cleans up the spkg-install file.
Please review:
http://trac.sagemath.org/sage_trac/ticket/13237
--
--
To post to this group, send an email
On 3/08/2012, at 4:08 PM, Dima Pasechnik wrote:
>
> On Thursday, 2 August 2012 23:00:23 UTC+8, kfiz wrote:
>>
>> yes, I'm trying to build sage in the "Applications" folder.
>
>
> I'm not a big OSX expert, but I might expect that one needs to use sudo
> sometimes to change things there proper
On 2012-08-03 03:46, John H Palmieri wrote:
> Given the number of people who have problems installing Sage because
> their system is missing openssl, should we check for that in the prereq
> script, so that the error is caught as soon as possible, and so that we
> can write a good error message? (N
On 2012-08-03 04:16, Volker Braun wrote:
> If you are going to add this, maybe you can also add dpkg-architecture
> on Ubuntu. This prerequisite (to figure out multiarch) one took me a
> while to figure out, and it wasn't installed on the Ubuntu box that I
> played with.
And how are you going to fi
On Aug 2, 4:58 pm, I wrote:
> cProfile.run(cmd, DATA + "profdata")
For future reference, my next command was going to be
s=pstats.Stats(DATA +"profdata")
in which case one can avoid using the temporary file altogether by
doing
import cProfile,pstats
s=pstats.Stats(cProfile.Profile().run(cmd))
On Aug 2, 7:43 pm, William Stein wrote:
> If the data is ephemeral, you could use the tempfile module.
Thanks! excellent suggestion. For future reference:
If you do:
import tempfile
F=tempfile.NamedTemporaryFile()
then you have a usable (existing) filename F.name
Beware that once the referenc
On 8/2/12 9:54 PM, fero wrote:
Il giorno venerdě 3 agosto 2012 05:13:09 UTC+2, jason ha scritto:
On 8/2/12 9:08 AM, fero wrote:
> It seems strange to me that the newest sagecell server source
package
> documented in github repo,
> fails to install in the recently released
Il giorno venerdì 3 agosto 2012 05:13:09 UTC+2, jason ha scritto:
>
> On 8/2/12 9:08 AM, fero wrote:
> > It seems strange to me that the newest sagecell server source package
> > documented in github repo,
> > fails to install in the recently released sage. I thought that this
> > were
>
On Thursday, 2 August 2012 23:00:23 UTC+8, kfiz wrote:
>
> yes, I'm trying to build sage in the "Applications" folder.
I'm not a big OSX expert, but I might expect that one needs to use sudo
sometimes to change things there properly.
I would rather build in a "normal" user directory, and then
On 8/2/12 9:08 AM, fero wrote:
It seems strange to me that the newest sagecell server source package
documented in github repo,
fails to install in the recently released sage. I thought that this
were
one of the first things you tested before releasing the new sage :))
Right now, the sage
On Thursday, August 2, 2012, Nils Bruin wrote:
> I noticed that on more "public" notebooks, where the sage worker
> processes run under a different UID than the notebook server, there is
> a problem that "DATA" is generally not writable by the worker. That
> means that, for instance for profiling,
On Thursday, August 2, 2012, Volker Braun wrote:
> If you are going to add this, maybe you can also add dpkg-architecture on
Ubuntu. This prerequisite (to figure out multiarch) one took me a while to
figure out, and it wasn't installed on the Ubuntu box that I played with.
> Just today I was also
On Thursday, August 2, 2012 5:42:01 PM UTC-4, François wrote:
>
> That's not unusual for a binary to be relinked at install time.
+1
The whole rpath mess is something that we'll have to fix one day.
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
If you are going to add this, maybe you can also add dpkg-architecture on
Ubuntu. This prerequisite (to figure out multiarch) one took me a while to
figure out, and it wasn't installed on the Ubuntu box that I played with.
Just today I was also thinking about adding a script in front of the whol
As one who was bit by this, +1.
On Thursday, August 2, 2012 8:46:47 PM UTC-5, John H Palmieri wrote:
>
> Given the number of people who have problems installing Sage because their
> system is missing openssl, should we check for that in the prereq script,
> so that the error is caught as soon as
Given the number of people who have problems installing Sage because their
system is missing openssl, should we check for that in the prereq script,
so that the error is caught as soon as possible, and so that we can write a
good error message? (Note that I'm not volunteering to do this, because
I noticed that on more "public" notebooks, where the sage worker
processes run under a different UID than the notebook server, there is
a problem that "DATA" is generally not writable by the worker. That
means that, for instance for profiling, the command
cProfile.run(cmd, DATA + "profdata")
will
On 3/08/2012, at 2:12 AM, Anna Haensch wrote:
>
> What's the protocol then for reviewing patches on my machine at the moment?
> I guess it's impossible to get "all tests passed" with my current install.
Try building from source. It should work on 10.6.8, with all doctests passing.
--
--
To
On Thu, 02 Aug 2012 22:10:44 Jeroen Demeyer wrote:
> On 2012-08-02 18:50, Jean-Pierre Flori wrote:
> > Hi all,
> >
> > While looking at the pari spkg and the build logs, I remarked that the
> > final library and gp files are linked twice.
> > Once by make gp and once by make install (which deletes
On Thursday, August 2, 2012 4:09:59 PM UTC-4, Jeroen Demeyer wrote:
>
> On 2012-08-02 22:06, Luis Finotti wrote:
> > libssl-dev - SSL development libraries, header files and
> documentation
> This is the one.
>
Thanks! I've installed it and will try again overnight.
--
--
To post
On 2012-08-02 18:50, Jean-Pierre Flori wrote:
> Hi all,
>
> While looking at the pari spkg and the build logs, I remarked that the
> final library and gp files are linked twice.
> Once by make gp and once by make install (which deletes them and relink
> them...)
I can only confirm this fact, but t
On 2012-08-02 22:06, Luis Finotti wrote:
> libssl-dev - SSL development libraries, header files and documentation
This is the one.
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.c
Thanks for the reply!
On Thursday, August 2, 2012 3:54:55 PM UTC-4, Jeroen Demeyer wrote:
>
> You need to install OpenSSL and its "development headers".
>
Could you be more specific? Do you mean:
openssl - Secure Socket Layer (SSL) binary and related cryptographic
tools
or the Python on
You need to install OpenSSL and its "development headers".
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage
Dear all,
I tried to build 5.2 from source. I am running Aptosid Linux (basically
Debian Sid) with kernel 3.5. This is on a Levovo T510.
Some system info:
Host/Kernel/OS "t510" running Linux 3.5-0.slh.1-aptosid-amd64 x86_64 [
sidux 2010-01 Ύπνος - kde-full - (201006131622)
]
I guess I should also send that to the pari crew as its the behavior of
their build system.
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at h
Hi all,
While looking at the pari spkg and the build logs, I remarked that the
final library and gp files are linked twice.
Once by make gp and once by make install (which deletes them and relink
them...)
Also on Cygwin some .dll.a file which it would be nice to have never gets
"installed".
In
Deal all,
I have just downloaded sage-5.2 compiled for ubuntu lts 12.04.
I am on ArchLinux.
I'd like to try sagecell server as kcrisman suggested me on
http://ask.sagemath.org/question/1623/notebook-api-new-worksheet
(thx)
but some patches fail to apply.
So I write to you as it is described in i
yes, I'm trying to build sage in the "Applications" folder.
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sag
I did built from binaries. My computer was not particularly busy...so I'm
not sure what the deal is with that.
What's the protocol then for reviewing patches on my machine at the moment?
I guess it's impossible to get "all tests passed" with my current install.
Is this sort of problem usual
On 2012-08-02 16:00, Anna Haensch wrote:
> Hi All,
>
> I just installed 5.2 on OS X 10.6.8. Immediately after the build, I ran
>
> $ ./sage -tp 10 long devel/sage-main/
>
> and without applying any new patches, got several doctest failures:
>
> sage -t devel/sage-main/sage/databases/sql_db.p
Hi All,
I just installed 5.2 on OS X 10.6.8. Immediately after the build, I ran
$ ./sage -tp 10 long devel/sage-main/
and without applying any new patches, got several doctest failures:
sage -t devel/sage-main/sage/databases/sql_db.py # 14 doctests failed
sage -t devel/sage-main/sage/graphs
34 matches
Mail list logo
