It's still down.
--
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-devel
URL: http://www.sagemath.org
On Thursday, 1 December 2011 10:57:21 UTC+8, kcrisman wrote:
>
> On Nov 30, 9:38 pm, Dima Pasechnik wrote:
> > On Thursday, 1 December 2011 05:40:35 UTC+8, Juanjo wrote:
> >
> > > On Wed, Nov 30, 2011 at 9:32 PM, kcrisman wrote:
> >
> > >> That is weird that you have to do this. Juanjo suggest
On 11/30/2011 09:04 PM, kcrisman wrote:
>
>
> On Nov 30, 6:37 pm, Michael Orlitzky wrote:
>> What's the correct procedure to confirm a ticket is invalid or otherwise
>> fixed. Status -> positive review, to get attention?
>>
>
> It looks like that is the current way we do it. Make sure to set t
On Nov 30, 9:38 pm, Dima Pasechnik wrote:
> On Thursday, 1 December 2011 05:40:35 UTC+8, Juanjo wrote:
>
> > On Wed, Nov 30, 2011 at 9:32 PM, kcrisman wrote:
>
> >> That is weird that you have to do this. Juanjo suggested that he had
> >> made a bunch of changes to totally change how forking w
On Thursday, 1 December 2011 05:40:35 UTC+8, Juanjo wrote:
>
> On Wed, Nov 30, 2011 at 9:32 PM, kcrisman wrote:
>
>> That is weird that you have to do this. Juanjo suggested that he had
>> made a bunch of changes to totally change how forking works in ECL
>> this summer, but maybe they weren't
On Nov 30, 6:37 pm, Michael Orlitzky wrote:
> What's the correct procedure to confirm a ticket is invalid or otherwise
> fixed. Status -> positive review, to get attention?
>
It looks like that is the current way we do it. Make sure to set the
milestone to sage-invalid or something.
However,
On Nov 30, 4:40 pm, Juan Jose Garcia-Ripoll
wrote:
> On Wed, Nov 30, 2011 at 9:32 PM, kcrisman wrote:
> > That is weird that you have to do this. Juanjo suggested that he had
> > made a bunch of changes to totally change how forking works in ECL
> > this summer, but maybe they weren't merged?
What's the correct procedure to confirm a ticket is invalid or otherwise
fixed. Status -> positive review, to get attention?
Reference:
http://trac.sagemath.org/sage_trac/ticket/3447
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send a
On Wed, Nov 30, 2011 at 9:32 PM, kcrisman wrote:
> That is weird that you have to do this. Juanjo suggested that he had
> made a bunch of changes to totally change how forking works in ECL
> this summer, but maybe they weren't merged? I'm cc:ing him on this.
I did not change the way fork is u
The python spkg should not use "parallel install". This is claimed to be
fixed in the spkg, but it actually isn't done properly. There are some
comments in spkg-install about how to fix it.
Also, the python library should be installed with writable permission
0755, instead of 0555. See an earlier
At #12098, I have a patch which makes the readline spkg depend on the
termcap spkg. This is how things should be, because readline does use
termcap.
Please review http://trac.sagemath.org/sage_trac/ticket/12098
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscrib
On Nov 30, 12:55 pm, Dima Pasechnik wrote:
> I guess I figured this out. This problem was in weird behavior of
> capitalization of filenames and directory names, and/or in the fact that
> I was building in a subdirectory of the home directory of a WIndows domain
> user...
>
> Moving the build tr
I guess I figured this out. This problem was in weird behavior of
capitalization of filenames and directory names, and/or in the fact that
I was building in a subdirectory of the home directory of a WIndows domain
user...
Moving the build tree to a saner place fixed this weirdness.
And then I wa
On Wed, Nov 30, 2011 at 06:12:16AM -0800, Dima Pasechnik wrote:
> OK, that's for lisp experts among us, it seems.
> I have no idea why it shouldn't have worked then.
Would you like me to do a 'virgin' build with just the
updated readline library, just to have a clean base test
to work against?
Hi Dima,
On 30 Nov., 15:29, Dima Pasechnik wrote:
> I might get blamed for making discouraging remarks, but let me play the
> devil's advocate:
>
> I wonder if these kinds of speed-ups are to be beaten, soon, by
> sufficiently fast hardware implementations of level 2 and 3 BLAS, coupled
> with so
I might get blamed for making discouraging remarks, but let me play the
devil's advocate:
I wonder if these kinds of speed-ups are to be beaten, soon, by
sufficiently fast hardware implementations of level 2 and 3 BLAS, coupled
with some crude use of their super-fast vector arithmetic.
Assumin
OK, that's for lisp experts among us, it seems.
I have no idea why it shouldn't have worked then.
--
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
Hi Jeroen,
On 30 Nov., 14:48, Jeroen Demeyer wrote:
> The easiest solution here would be making meataxe a standard spkg
> directly. Ask William whether you can do this...
I guess making it standard would require to (1) make it an optional
package first, and (2) have a vote on sage-devel.
Cheer
On 2011-11-30 14:36, Simon King wrote:
> Unfortunately, one has to apply the spkg *and* a patch to the Sage
> library. Is it possible to do those things in one step? That's to say:
> Is spkg-install allowed to patch the Sage library and rebuild Sage?
I don't think so ;-)
The easiest solution here
On Wed, Nov 30, 2011 at 04:33:28AM -0800, Dima Pasechnik wrote:
> after all, it seems you need more things to be installed: the autotools
> chain, i.e.
> autoconf and automake.
> I suppose it's autotools-dev package on oneiric.
They appear to already be installed:
*** Opt develautoconf
Hi All!
I have opened trac ticket #12103, needing review. The proposal is to
make the modified MeatAxe (among other things, I added Strassen-
Winograd multiplication to it) an optional package, i.e., an optional
back end for linear algebra over GF(p^n), p>2 prime, n>1, p^n<255. It
is *much* faster
Fixed in
http://trac.sagemath.org/sage_trac/ticket/12096
--
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-devel
I had the same issue with "make micro_release" tripping over a
non-writeable libpython2.6.so in
http://trac.sagemath.org/sage_trac/ticket/11743#comment:2
My vote would be to set permissions to 755. But note that if you modify
libpython then currently running python processes can and will segfau
after all, it seems you need more things to be installed: the autotools
chain, i.e.
autoconf and automake.
I suppose it's autotools-dev package on oneiric.
Are they installed? If not, please install them, and re-run
./sage -f spkg/standard/maxima-5.23.2.p0.spkg
--
To post to this group, send a
On Wed, Nov 30, 2011 at 03:19:32AM -0800, Dima Pasechnik wrote:
> and what about
> ls -l /root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-5.23.
> 2.p0/src/src/binary-ecl/*
> ?
> Any files there at all?
ls -l
/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-5.23.2.p0/src/src/binary-ecl
On Wednesday, 30 November 2011 19:10:54 UTC+8, DaleAmon wrote:
>
> On Wed, Nov 30, 2011 at 03:06:50AM -0800, Dima Pasechnik wrote:
> > The log says:
> >
> > Filesystem error with pathname
> > #P"/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-
> > 5.23.2.p0/src/src/binary-ecl/maxima-packag
The shared library local/lib/libpython2.6.dylib/dll/so is created with
permissions 555.
Is there any reason for this?
I noticed this, as I needed to rebase it on Cygwin, and needed to change it
to 755 manually.
Can this be made 755 all the time?
Thanks,
Dima
--
To post to this group, send an e
On Wed, Nov 30, 2011 at 03:06:50AM -0800, Dima Pasechnik wrote:
> The log says:
>
> Filesystem error with pathname
> #P"/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-
> 5.23.2.p0/src/src/binary-ecl/maxima-package.fas".Either
> 1) the file does not exist, or 2) we are not allow to access th
The log says:
Filesystem error with pathname
#P"/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-
5.23.2.p0/src/src/binary-ecl/maxima-package.fas".Either
1) the file does not exist, or 2) we are not allow to access the file,
or 3) the pathname points to a broken symbolic link..
So, what does
On Tue, Nov 29, 2011 at 07:52:47PM -0800, Dima Pasechnik wrote:
> Well, welcome to the bleeding edge development. :)
> Oneiric is not currently supported by Sage, as you probably know.
> No, it's not something to do with debian packages, it's most certainly
> Sage's internal issue.
> It could be
Somebody please review:
On 2011-11-21 15:21, Jeroen Demeyer wrote:
> Currently, sage -sdist changes the version number in the *current*
> branch devel/sage but it then makes a distribution from *main* branch
> devel/sage-main. I think it would be better to make the distribution
> always from deve
At #12097, I have a patch which essentially rewrites
SAGE_ROOT/local/bin/sage-make_relative. The new code is cleaner and
simpler. It also changes files only once and only when needed. The
previous version changed every Python file every time sage-make_relative
was run. Another consequence is tha
32 matches
Mail list logo
