"Georg S. Weber" writes:
> On 14 Mrz., 20:43, Jeroen Demeyer wrote:
>> On 2012-03-14 19:20, Keshav Kini wrote:> If we switch to git, as I
>> understand we eventually will, patches
>> > (commits) made from an older dev release will be considered to "not
>> > apply" (not be mergeable) a lot more o
On 15 Mrz., 07:12, Simon King wrote:
> I installed
> * a modified PPL 0.11.2 spkg, that also installs a C interface,
> * a CLooG-PPL 0.15.11 spkg
> * a modified gcc 4.6.3 spkg, that builds gcc with graphite.
And I forgot: I also upgraded the optional GMP spkg (GMP is required
by CLooG). Our old s
Hi Dan
On 15 March 2012 02:05, Dan Drake wrote:
> > sudo apt-add-repository ppa:aims/sagemath
> > sudo apt-get update
> > sudo apt-get install sagemath-upstream-binary
>
> I tried this in a 11.10 virtual machine, and it created the user's .sage
> directory as owned by root -- with 700 permissio
Hi Leif, hi all,
On 15 Mrz., 04:13, leif wrote:
> So what we currently need is CLooG-PPL 0.15.11, and a suitable version
> of PPL. (I'm not 100% sure that PPL 0.11.2, the version currently
> shipped with Sage, works, but /I think/(tm) it will...)
I installed
* a modified PPL 0.11.2 spkg, that a
On Mar 14, 10:25 am, Simon King wrote:
> On 14 Mrz., 10:17, Simon King wrote:
>
> > The first thing I tried was CLooG 0.17.0, not using --with-ppl. That
> > has not been enough for your gcc spkg.
>
> To be precise:
> PPL with C interface and CLooG 0.17.0 not using --with-ppl => no
> success
>
On Tue, 28 Feb 2012 at 09:50PM +0100, Jan Groenewald wrote:
> The deb available below was not built from source on launchpad, instead
> it is the sage upstream binary built for Ubuntu 10.04.3 hammered into a
> PPA for lucid, maverick natty, oneiric, and precise in the ugliest possible
> way.
>
> I
On Wed, Mar 14, 2012 at 2:10 PM, Georg S. Weber
wrote:
> On 14 Mrz., 20:43, Jeroen Demeyer wrote:
>> On 2012-03-14 19:20, Keshav Kini wrote:> If we switch to git, as I
>> understand we eventually will, patches
>> > (commits) made from an older dev release will be considered to "not
>> > apply" (
On 14 Mrz., 20:43, Jeroen Demeyer wrote:
> On 2012-03-14 19:20, Keshav Kini wrote:> If we switch to git, as I understand
> we eventually will, patches
> > (commits) made from an older dev release will be considered to "not
> > apply" (not be mergeable) a lot more often than merely the cases when
On Feb 27, 3:24 pm, kcrisman wrote:
> On Feb 27, 1:31 pm, William Stein wrote:
>
> > Hi,
>
> > Why is the default color for an ellipse (and circle) *black*, whereas
> > the default color for (msot) everything else (even text) is blue?
>
> The default color for circles *was* blue when they were
On Wednesday, 14 March 2012 18:33:49 UTC, William stein wrote:
>
> On Wed, Mar 14, 2012 at 11:22 AM, William Stein wrote:
> > Hi,
> >
> > A circuit breaker was blown by yet another power issue. Fortunately,
> > the sysadmin strong some temporary power, and at least most services
> > are restar
On 2012-03-14 19:20, Keshav Kini wrote:
> If we switch to git, as I understand we eventually will, patches
> (commits) made from an older dev release will be considered to "not
> apply" (not be mergeable) a lot more often than merely the cases when
> other people have meanwhile touched the same fil
On Wed, Mar 14, 2012 at 11:22 AM, William Stein wrote:
> Hi,
>
> A circuit breaker was blown by yet another power issue. Fortunately,
> the sysadmin strong some temporary power, and at least most services
> are restarted. http://sagenb.org isn't (since mod is still off), but
sagenb.org should
Hi,
A circuit breaker was blown by yet another power issue. Fortunately,
the sysadmin strong some temporary power, and at least most services
are restarted. http://sagenb.org isn't (since mod is still off), but
at least http://*.sagenb.org is back for all *'s, trac is back, etc.
-- William
O
"Georg S. Weber" writes:
> 1.
> It can guarantee that each "official" release depends linearly on the
> previous oficial release. I.e. there is a well defined (and openly
> communicated/visible) series of patches, that will lead from one
> official release to the next/following one, when these pat
The trac server, which has been up all day, now seems to have gone back
down again.
David
--
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:/
Hi,
I'm aware that a few minutes ago the entire sage.math cluster
"vanished" from the internet. I know nothing about why yet. Until
this is resolved, all services are unavailable, obviously.
William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
To
On Wed, Mar 14, 2012 at 9:55 AM, Georg S. Weber
wrote:
> Finally, I'd like to add that in my eyes, Jeroen does a tremendously
> good job in "coordinating concurrent or conflicting changes", to the
> extent that more often than not, it is us fellow developers hanging
> behind after him, not the oth
>
> Frankly said, it is currently *too easy* (for the release manager) to
> abandon changes made to previous, already published [devel] releases
> -- as if they never happened. And whether that's beneficial to the
> development and review process is at least questionable.
>
> 2ct,
>
> -leif
Hi L
On Wed, Mar 14, 2012 at 1:59 AM, P Purkayastha wrote:
> WFM.
The server was temporarily down due to a power plant failure.
William
>
>
> On Wednesday, March 14, 2012 7:57:54 AM UTC+8, aw1231 wrote:
>>
>> looks bad on my end too!
>
> --
> To post to this group, send an email to sage-devel@google
On Wed, Mar 14, 2012 at 3:05 AM, Simon King wrote:
> Hi!
>
> On 14 Mrz., 10:06, David Loeffler wrote:
>> ... and now it's back up again. Thanks!
>
> I can still not connect with sage.math.washington.edu. scp tells me
> that the connection timed out.
To quote from my previous email: "Also, the co
Hi!
On 14 Mrz., 10:06, David Loeffler wrote:
> ... and now it's back up again. Thanks!
I can still not connect with sage.math.washington.edu. scp tells me
that the connection timed out.
Cheers,
Simon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from th
On 14 Mrz., 10:17, Simon King wrote:
> The first thing I tried was CLooG 0.17.0, not using --with-ppl. That
> has not been enough for your gcc spkg.
To be precise:
PPL with C interface and CLooG 0.17.0 not using --with-ppl => no
success
Adding CLooG-PPL 0.15.11 not using --with-ppl => no suc
Hi Jeroen,
On 14 Mrz., 09:52, Jeroen Demeyer wrote:
> The reason they dropped the "-PPL" suffix is that CLooG 0.16 doesn't
> need PPL as build-time dependency. CLooG-PPL needs PPL at build-time
> (that's why you need the --with-ppl option). GCC with Graphite needs
> PPL itself and CLooG(-PPL) 0
On Wednesday, 14 March 2012 08:38:57 UTC, David Loeffler wrote:
> It looks like the patchbot server, at patchbot.sagemath.org, is still
> down.
>
> David
>
... and now it's back up again. Thanks!
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
WFM.
On Wednesday, March 14, 2012 7:57:54 AM UTC+8, aw1231 wrote:
>
> looks bad on my end too!
>
--
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
On 2012-03-14 09:46, Simon King wrote:
> cloog is different from cloog-ppl
I understand it that CLooG is the logical continuation of CLooG-PPL, so
it is the same software. CLooG-PPL 0.15 was followed by CLooG 0.16.
The reason they dropped the "-PPL" suffix is that CLooG 0.16 doesn't
need PPL as b
Hi Jeroen,
On 14 Mrz., 09:27, Jeroen Demeyer wrote:
> On 2012-03-14 07:24, Simon King wrote:> * CLooG needs GMP.
>
> Are you sure it doesn't work with MPIR?
When I first tried to install CLooG, then it failed and told me that
GMP is missing. That's why I said GLooG needs GMP.
However, I could
On Wednesday, 14 March 2012 03:37:27 UTC, William stein wrote:
>
> Quick update:
>
>* http://aleph.sagemath.org is up now, as Jason mentioned.
>
>* Absolutely *none* of the external disks attached to any of the
> machines have appeared, so I can only guess something weird happened
> with a
On Wed, Mar 14, 2012 at 09:27:21AM +0100, Jeroen Demeyer wrote:
> On 2012-03-14 07:24, Simon King wrote:
> > * CLooG needs GMP.
> Are you sure it doesn't work with MPIR?
Incidentally, Cédric Bastoul, the author of CLooG is working is the same
research lab as me and teaching is the same department
Probably GAP uses some of the GMP internals. As far as I know, we
don't test MPIR against GAP. It sounds like we should.
Bill.
On 14 March 2012 02:55, William Stein wrote:
> Hi MPIR devs
>
> Do any of you know what Dima is alluding to below?
>
>
> -- Forwarded message --
> From:
On 2012-03-14 07:24, Simon King wrote:
> * CLooG needs GMP.
Are you sure it doesn't work with MPIR?
--
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
On 2012-03-14 02:07, John H Palmieri wrote:
> I guess the answer to your question is yes, though: even with OS X 10.6
> or earlier, the proposal is to build gcc.
Since Xcode doesn't include a Fortran compiler and the Fortran spkg will
be removed, we *have* to build GCC anyway for gfortran.
--
To
On 2012-03-14 01:11, Dima Pasechnik wrote:
> You seem to indicate this will not be used to build Sage any more.
> Right?
Exactly.
> (even though this is a working setup, as far as Sage 5.0.beta* are
> concerned...
Well, is there anything wrong with replacing a working setup by a
different working
33 matches
Mail list logo
