[sage-support] Re: Sage-2.9

[mabshoff]

On Jan 4, 5:15 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:

Hi Kiran,

> If I describe my setup, it might seem less uncommon than you might
> have previously thought.
>
> Mine is a 64-bit box on a network consisting mostly of 32-bit
> machines. On my machine, /usr/bin is locally mounted, and there is a
> local 64-bit gcc there.
>
> But /usr/local is NFS mounted, and there is a 32-bit gcc in /usr/local/
> bin for the benefit of the benighted masses. Persuading my sysadmin to
> instead install a local 32-bit gcc on every single 32-bit machine in
> the department is not going to happen.

I understand, but providing 32 bit compilers to 64 bit machines seems
a little silly. At least in the setups I have run we had different NFS
exports for 32 and 64 bit Linux boxen.

> So I have to switch rather than fight. My $PATH has /usr/bin ahead of /
> usr/local/bin, so ordinarily (and even in SCons if I force it to
> import my PATH environment variable) this causes no problems.
>
> But SCons defaults not to importing any environment variables, which
> means it has to come up with its own guess for the path. And what it
> comes up with on my box is:
>/usr/local/bin:/opt/bin:/bin:/usr/bin
> I have no idea why. There isn't even a directory /opt/bin on my
> system! This might be some sort of hard-coded default (either in SCons
> or in the RHEL configs somewhere).

SCons is at fault: From local/lib/scons-0.97/SCons/Platform/posix.py

if not env.has_key('ENV'):
env['ENV']= {}
env['ENV']['PATH']= '/usr/local/bin:/opt/bin:/bin:/usr/bin'


> Anyway, I'm able to manually patch the relevant SConstruct files to
> get around this, so it's not a high priority for me to get this fixed.
> But I suspect that sooner or later, someone else will run into this if
> nothing is done about it.

So as a solution I would suggest to import ENV into the PolyBoRi SCons
build system. Feel free to submit a patch for it.

> Kiran

I am also attaching the same into to #1553.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[[EMAIL PROTECTED]]

If I describe my setup, it might seem less uncommon than you might
have previously thought.

Mine is a 64-bit box on a network consisting mostly of 32-bit
machines. On my machine, /usr/bin is locally mounted, and there is a
local 64-bit gcc there.

But /usr/local is NFS mounted, and there is a 32-bit gcc in /usr/local/
bin for the benefit of the benighted masses. Persuading my sysadmin to
instead install a local 32-bit gcc on every single 32-bit machine in
the department is not going to happen.

So I have to switch rather than fight. My $PATH has /usr/bin ahead of /
usr/local/bin, so ordinarily (and even in SCons if I force it to
import my PATH environment variable) this causes no problems.

But SCons defaults not to importing any environment variables, which
means it has to come up with its own guess for the path. And what it
comes up with on my box is:
   /usr/local/bin:/opt/bin:/bin:/usr/bin
I have no idea why. There isn't even a directory /opt/bin on my
system! This might be some sort of hard-coded default (either in SCons
or in the RHEL configs somewhere).

Anyway, I'm able to manually patch the relevant SConstruct files to
get around this, so it's not a high priority for me to get this fixed.
But I suspect that sooner or later, someone else will run into this if
nothing is done about it.

Kiran

On Jan 2, 12:01 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On Dec 29 2007, 1:58 am, "Kiran Kedlaya" <[EMAIL PROTECTED]> wrote:
>
>
>
> > I posted an install log (for SAGE 2.9.1.1) here:
>
> >http://sage.math.washington.edu/home/kedlaya/install.log
>
> > And re my compiler version: the result of gcc -v is:
>
> > Using built-in specs.
> > Target: x86_64-redhat-linux
> > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> > --infodir=/usr/share/info --enable-shared --enable-threads=posix
> > --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> > --disable-libunwind-exceptions --enable-libgcj-multifile
> > --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> > --enable-java-awt=gtk --disable-dssi --enable-plugin
> > --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> > --with-cpu=generic --host=x86_64-redhat-linux
> > Thread model: posix
> > gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
>
> > Kiran
>
> Hello,
>
> with Kiran's help we finally tracked this down while in IRC. SCons
> picks another gcc that is in $PATH, namely one in /usr/local/bin:
>
> Target: i686-pc-linux-gnu
> Configured with: ./configure --prefix=/usr/local/pkg/gcc-4.2.0 --
> enable-languages=c,c++,fortran,java,objc,obj-c++
> Thread model: posix
> gcc version 4.2.0
>
> But that one is a 32 bit target, so things go *boom*.
>
> This should be a very uncommon setup, but we still hit it. So I have
> made this #1656.
>
> Cheers,
>
> Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 29 2007, 1:58 am, "Kiran Kedlaya" <[EMAIL PROTECTED]> wrote:
> I posted an install log (for SAGE 2.9.1.1) here:
>
> http://sage.math.washington.edu/home/kedlaya/install.log
>
> And re my compiler version: the result of gcc -v is:
>
> Using built-in specs.
> Target: x86_64-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi --enable-plugin
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=x86_64-redhat-linux
> Thread model: posix
> gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
>
> Kiran

Hello,

with Kiran's help we finally tracked this down while in IRC. SCons
picks another gcc that is in $PATH, namely one in /usr/local/bin:

Target: i686-pc-linux-gnu
Configured with: ./configure --prefix=/usr/local/pkg/gcc-4.2.0 --
enable-languages=c,c++,fortran,java,objc,obj-c++
Thread model: posix
gcc version 4.2.0

But that one is a 32 bit target, so things go *boom*.

This should be a very uncommon setup, but we still hit it. So I have
made this #1656.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Kiran Kedlaya]

I posted an install log (for SAGE 2.9.1.1) here:

http://sage.math.washington.edu/home/kedlaya/install.log

And re my compiler version: the result of gcc -v is:

Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi --enable-plugin
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=x86_64-redhat-linux
Thread model: posix
gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)

Kiran


On 12/27/07, Burcin Erocal <[EMAIL PROTECTED]> wrote:
> Hello Kiran,
>
> On Mon, 17 Dec 2007 08:05:29 -0800 (PST)
> mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Dec 17, 2:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > > I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
> > > upgrade dies pretty definitively at PolyBoRi. As far as I can tell,
> > > on the first file it is throwing lots of compile errors of the form
> > >
> > > /tmp/cciylcHI.s:17647: Error: suffix or operands invalid for `push'
> > > /tmp/cciylcHI.s:17697: Error: suffix or operands invalid for `pop'
> > >
> > > I'm guessing/hoping this is probably some easy fix on my end. Any
> > > suggestions?
> >
> > That is a bashism that was supposedly fixed by Burcin. It might have
> > snuck back into the latest spkg. I will investigate this. rlm created
> > #1553 for this.
>
> This is probably a compiler error, unrelated to the bashisms I fixed in
> spkg-install. The original error was caused by using popd and pushd,
> which are bash conveniences. The file in this error is a temporary
> (guessing from the extension) assembly file generated during the
> build, and the error message says "push" not "pushd". :)
>
> Michael A is the expert on these build problems, but let me still ask:
>
> Can you provide more information on your compiler? and maybe put a copy
> of the build log somewhere?
>
> Burcin
>

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage 2.9 VMWare image released

[William Stein]

On Dec 27, 2007 9:37 PM, Adam Getchell <[EMAIL PROTECTED]> wrote:
>
> On Dec 22, 2007 1:16 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> > Did you first run the VMware vmshrink utility, then turn the vmware
> > machine off and exit vmware before creating the 7z file?  Also,
> > how big is your vmware-sage-deluxe when uncompressed?
>
> vmshrink gives the result "disk compression disabled". I compiled
> vmshrink from source and used the pre-built binary to doublecheck,
> I'll have to look into my VMware workstation settings to see if I've
> got something off.

I remember vaguely seeing that error message once.  You definitely
want to fix that, as it will make a _huge_ difference.I don't remember
the fix, except I found it by googling around for a bit.

> vmware-sage-deluxe (nice name) was about 6.8 Gb as of 2.9. It's a bit
> bigger now, but I'll check into reducing it.
>
> > Do you think you could somewhat commit to making new vmware
> > sage releases for "the next 2-3 months", say?
>
> Sure! I'm upgrading Sage to 2.9.1 right now. In order of priority, I'm
> working on:
>
> 1. Upgrade to 2.9.1 (and follow-ons)

If you do "sage -upgrade" you'll get 2.9.1.1

> 2. shrink with vmtools
> 3. Secure some space for regular uploads (checking with our local
> cluster group right now for access)

Send me an offlist email, and I can make an account for you on
sage.math.washington.edu

> 4. Bundle in vmtools for better graphics performance (last time I
> tried, required rpm tools, and didn't build)

It's *very* important that the "deluxe" sage vmware machine have the
vmware tools
fully working.  This makes a big difference -- e.g., the mouse will
move in and out
of the virtual machine more easily, etc.

> 5. Build version with more generic monitor resolutions

Very likely if you had vmware tools working it would automatically
resize the display
to whatever resolution the user selects (or however they resize their
vmware image).
Getting vmware tools working well is always the first step...
By the way, the vmware "virtual marketplace" has tons pre-made virtual machines.
It's possible you could find one, add Sage to it, and be good to go.  I've tried
that before and been disappointed though.

It would also be very good if a Sage virtual machine could be listed in the
VMware tools virtual marketplace.  I filled out the forms to get SAge listed
once, and they were completely ignored (I heard nothing back from vmware).
Perhaps you would have better luck?

> I also need some time to look over how you're doing a build from
> scratch, to see if I'm off or there's other things that could be done.

I just do a straight build.  Then i replace all the spkg' files in spkg/standard
by empty files, using the command /usr/local/bin/shrink that I wrote.

> > Optimally we would just included it on the main sagemath.org website
> > under downloads, and mirror it out to the mirrors.
>
> Okay. I'm a little short on space to put the image up for you to look
> at right now, but I expect to get a vmware-sage-deluxe image available
> for download so you can look it over in the first week of January or
> so.
>

OK.

> What a great tool! I was just giving up on Python for scientific
> programming,

Thanks!

> as they'd taken steps away from functional programming in
> Python 3000.

I'm worried about that too.   :-(   What's the latest on it?

Anyway, it will be at least a year (minimum; probably more)
until Sage is using  Python 3000.

 -- William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage 2.9 VMWare image released

[Adam Getchell]

On Dec 22, 2007 1:16 PM, William Stein <[EMAIL PROTECTED]> wrote:

> Did you first run the VMware vmshrink utility, then turn the vmware
> machine off and exit vmware before creating the 7z file?  Also,
> how big is your vmware-sage-deluxe when uncompressed?

vmshrink gives the result "disk compression disabled". I compiled
vmshrink from source and used the pre-built binary to doublecheck,
I'll have to look into my VMware workstation settings to see if I've
got something off.

vmware-sage-deluxe (nice name) was about 6.8 Gb as of 2.9. It's a bit
bigger now, but I'll check into reducing it.

> Do you think you could somewhat commit to making new vmware
> sage releases for "the next 2-3 months", say?

Sure! I'm upgrading Sage to 2.9.1 right now. In order of priority, I'm
working on:

1. Upgrade to 2.9.1 (and follow-ons)
2. shrink with vmtools
3. Secure some space for regular uploads (checking with our local
cluster group right now for access)
4. Bundle in vmtools for better graphics performance (last time I
tried, required rpm tools, and didn't build)
5. Build version with more generic monitor resolutions

I also need some time to look over how you're doing a build from
scratch, to see if I'm off or there's other things that could be done.

> Optimally we would just included it on the main sagemath.org website
> under downloads, and mirror it out to the mirrors.

Okay. I'm a little short on space to put the image up for you to look
at right now, but I expect to get a vmware-sage-deluxe image available
for download so you can look it over in the first week of January or
so.

What a great tool! I was just giving up on Python for scientific
programming, as they'd taken steps away from functional programming in
Python 3000.

>  -- William

Adam
-- 
"Invincibility is in oneself, vulnerability in the opponent." -- Sun Tzu

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Burcin Erocal]

Hello Kiran,

On Mon, 17 Dec 2007 08:05:29 -0800 (PST)
mabshoff <[EMAIL PROTECTED]> wrote:

> On Dec 17, 2:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:

> > I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
> > upgrade dies pretty definitively at PolyBoRi. As far as I can tell,
> > on the first file it is throwing lots of compile errors of the form
> >
> > /tmp/cciylcHI.s:17647: Error: suffix or operands invalid for `push'
> > /tmp/cciylcHI.s:17697: Error: suffix or operands invalid for `pop'
> >
> > I'm guessing/hoping this is probably some easy fix on my end. Any
> > suggestions?
> 
> That is a bashism that was supposedly fixed by Burcin. It might have
> snuck back into the latest spkg. I will investigate this. rlm created
> #1553 for this.

This is probably a compiler error, unrelated to the bashisms I fixed in
spkg-install. The original error was caused by using popd and pushd,
which are bash conveniences. The file in this error is a temporary
(guessing from the extension) assembly file generated during the
build, and the error message says "push" not "pushd". :)

Michael A is the expert on these build problems, but let me still ask:

Can you provide more information on your compiler? and maybe put a copy
of the build log somewhere?

Burcin

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage 2.9 VMWare image released

[William Stein]

On Dec 22, 2007 11:45 AM, Adam Getchell <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've created a VMWare image of Sage 2.9 running on gutsy with xubuntu-desktop.

Cool.  This could be the vmware-sage-deluxe.7z version.  We should have:
   vmware-sage-minimal
   vmware-sage-normal
   vmware-sage-deluxe


> Unfortunately, it's about 2.8G as a .zip file, or 2.2G as a .7z
> (7-zip, a free Windows utility), using ultra compression on both.

Did you first run the VMware vmshrink utility, then turn the vmware
machine off and exit vmware before creating the 7z file?  Also,
how big is your vmware-sage-deluxe when uncompressed?

Do you think you could somewhat commit to making new vmware
sage releases for "the next 2-3 months", say?

> I found that xfce seemed to be the only window manager that ran well
> (gnome and kde both failed). It has a large default monitor size that
> should be adjustable to whatever resolution you want using the
> standard tools, and I configured it for only 1 processor use (I use
> two on my workstation). In addition, it has all of the updates for
> gutsy and sage-2.9 as of yesterday.
>
> If there's some issue with video, let me know, I can revert to a
> snapshot and make something with a smaller default size (e.g. 1024 x
> 768).
>
> If there's interest in making this available, let me know and I'll
> make it available for posting to mirrors, or after the holidays, I may
> be able to find some server space of my own.

Optimally we would just included it on the main sagemath.org website
under downloads, and mirror it out to the mirrors.

 -- William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage 2.9 VMWare image released

[Adam Getchell]

Hi all,

I've created a VMWare image of Sage 2.9 running on gutsy with xubuntu-desktop.

Unfortunately, it's about 2.8G as a .zip file, or 2.2G as a .7z
(7-zip, a free Windows utility), using ultra compression on both.

I found that xfce seemed to be the only window manager that ran well
(gnome and kde both failed). It has a large default monitor size that
should be adjustable to whatever resolution you want using the
standard tools, and I configured it for only 1 processor use (I use
two on my workstation). In addition, it has all of the updates for
gutsy and sage-2.9 as of yesterday.

If there's some issue with video, let me know, I can revert to a
snapshot and make something with a smaller default size (e.g. 1024 x
768).

If there's interest in making this available, let me know and I'll
make it available for posting to mirrors, or after the holidays, I may
be able to find some server space of my own.

Adam
-- 
"Invincibility is in oneself, vulnerability in the opponent." -- Sun Tzu

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 19, 9:46 pm, "Adam Getchell" <[EMAIL PROTECTED]> wrote:
> On Dec 18, 2007 10:27 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
>
>
> > what happens if you type
>
> >  sudo sage -br
>
> I get the following errors during the process:
>
> sage/libs/mwrank/wrap.cc: In function 'double
> Curvedata_silverman_bound(const Curvedata*)':
> sage/libs/mwrank/wrap.cc:81: error: 'silverman_bound' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc: In function 'double
> Curvedata_cps_bound(const Curvedata*)':
> sage/libs/mwrank/wrap.cc:86: error: 'cps_bound' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'double
> Curvedata_height_constant(const Curvedata*)':
> sage/libs/mwrank/wrap.cc:91: error: 'height_constant' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc: In function 'char* Curvedata_getdiscr(Curvedata*)':
> sage/libs/mwrank/wrap.cc:97: error: 'getdiscr' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'char* Curvedata_conductor(Curvedata*)':
> sage/libs/mwrank/wrap.cc:103: error: 'CurveRed' was not declared in this scope
> sage/libs/mwrank/wrap.cc:103: error: expected `;' before 'E'
> sage/libs/mwrank/wrap.cc:105: error: 'E' was not declared in this scope
> sage/libs/mwrank/wrap.cc:105: error: 'getconductor' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc: In function 'char*
> Curvedata_isogeny_class(Curvedata*, int)':
> sage/libs/mwrank/wrap.cc:113: error: 'CurveRed' was not declared in this scope
> sage/libs/mwrank/wrap.cc:113: error: expected `;' before 'C'
> sage/libs/mwrank/wrap.cc:114: error: 'C' was not declared in this scope
> sage/libs/mwrank/wrap.cc:115: error: 'IsogenyClass' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc:115: error: expected `;' before 'cl'
> sage/libs/mwrank/wrap.cc:116: error: 'cl' was not declared in this scope
> sage/libs/mwrank/wrap.cc:117: error: 'vector' was not declared in this scope
> sage/libs/mwrank/wrap.cc:117: error: 'crs' was not declared in this scope
> sage/libs/mwrank/wrap.cc:118: error: 'Curve' was not declared in this scope
> sage/libs/mwrank/wrap.cc:118: error: 'cs' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'mw* mw_new(Curvedata*, int, int, int)':
> sage/libs/mwrank/wrap.cc:140: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc: In function 'void mw_del(mw*)':
> sage/libs/mwrank/wrap.cc:145: note: neither the destructor nor the
> class-specific operator delete will be called, even if they are
> declared when the class is defined.
> sage/libs/mwrank/wrap.cc: In function 'int mw_process(Curvedata*, mw*,
> const bigint*, const bigint*, const bigint*, int)':
> sage/libs/mwrank/wrap.cc:152: error: 'Point' was not declared in this scope
> sage/libs/mwrank/wrap.cc:152: error: expected `;' before 'P'
> sage/libs/mwrank/wrap.cc:153: error: 'P' was not declared in this scope
> sage/libs/mwrank/wrap.cc:155: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc:155: error: 'P' was not declared in this scope
> sage/libs/mwrank/wrap.cc: At global scope:
> sage/libs/mwrank/wrap.cc:159: error: expected ',' or '...' before '<' token
> sage/libs/mwrank/wrap.cc:159: error: ISO C++ forbids declaration of
> 'vector' with no type
> sage/libs/mwrank/wrap.cc: In function 'char* point_vector_to_str(int)':
> sage/libs/mwrank/wrap.cc:163: error: 'v' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'char* mw_getbasis(mw*)':
> sage/libs/mwrank/wrap.cc:174: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc: In function 'char* mw_regulator(mw*)':
> sage/libs/mwrank/wrap.cc:179: error: 'bigfloat' was not declared in this scope
> sage/libs/mwrank/wrap.cc:179: error: expected `;' before 'reg'
> sage/libs/mwrank/wrap.cc:181: error: 'reg' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'int mw_rank(mw*)':
> sage/libs/mwrank/wrap.cc:187: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc: In function 'int mw_saturate(mw*, bigint*,
> char**, long int, int)':
> sage/libs/mwrank/wrap.cc:194: error: 'vector' was not declared in this scope
> sage/libs/mwrank/wrap.cc:194: error: expected primary-expression before 'long'
> sage/libs/mwrank/wrap.cc:194: error: expected `;' before 'long'
> sage/libs/mwrank/wrap.cc:195: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc:195: error: 'v' was not declared in this scope
> sage/libs/mwrank/wrap.cc: At global scope:
> sage/libs/mwrank/wrap.cc:202: error: 'bigfloat' does not name a type
> sage/libs/mwrank/wrap.cc: In 

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 19, 7:10 pm, davedo2 <[EMAIL PROTECTED]> wrote:
> Michael,
>
> You had advised me to try the following command to adjust the laptop's
> performance:
>
> /usr/bin/cpufreq-selector -g performance
>
> However, cpufreq-selector doesn't appear to be available for kubuntu
> 7.10, at least I couldn't find it with either Adept or apt-get. I did
> install everything that related to cpufreq and found what seemed the
> closest, cpufreq-set. I blindly ran that with both the -g &
> performance arguments (although looking at the man later performance
> doesn't seem to apply.)
>
> In any event, the install then creeped slowly, but surely, to a
> successful completion. SAGE loads properly as does the notebook and
> the long test ran with no errors found.
>
> Thanks much for your help...Dave

Ok, good to know. I have updated the FAQ about using cpufreq-set on
Ubuntu/Debian. Since I don't have any of those systems locally it
would be nice if somebody could read the man page of cpufreq-set and
tell me what the recommended settings are.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[John Cremona]

My guess is that the conversion from the old mwrank package to the new
cremona package is muddling things up.

John

On 19/12/2007, Adam Getchell <[EMAIL PROTECTED]> wrote:
>
> On Dec 18, 2007 10:27 AM, William Stein <[EMAIL PROTECTED]> wrote:
> >
> > what happens if you type
> >
> >  sudo sage -br
>
> I get the following errors during the process:
>
> sage/libs/mwrank/wrap.cc: In function 'double
> Curvedata_silverman_bound(const Curvedata*)':
> sage/libs/mwrank/wrap.cc:81: error: 'silverman_bound' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc: In function 'double
> Curvedata_cps_bound(const Curvedata*)':
> sage/libs/mwrank/wrap.cc:86: error: 'cps_bound' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'double
> Curvedata_height_constant(const Curvedata*)':
> sage/libs/mwrank/wrap.cc:91: error: 'height_constant' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc: In function 'char* Curvedata_getdiscr(Curvedata*)':
> sage/libs/mwrank/wrap.cc:97: error: 'getdiscr' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'char* Curvedata_conductor(Curvedata*)':
> sage/libs/mwrank/wrap.cc:103: error: 'CurveRed' was not declared in this scope
> sage/libs/mwrank/wrap.cc:103: error: expected `;' before 'E'
> sage/libs/mwrank/wrap.cc:105: error: 'E' was not declared in this scope
> sage/libs/mwrank/wrap.cc:105: error: 'getconductor' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc: In function 'char*
> Curvedata_isogeny_class(Curvedata*, int)':
> sage/libs/mwrank/wrap.cc:113: error: 'CurveRed' was not declared in this scope
> sage/libs/mwrank/wrap.cc:113: error: expected `;' before 'C'
> sage/libs/mwrank/wrap.cc:114: error: 'C' was not declared in this scope
> sage/libs/mwrank/wrap.cc:115: error: 'IsogenyClass' was not declared
> in this scope
> sage/libs/mwrank/wrap.cc:115: error: expected `;' before 'cl'
> sage/libs/mwrank/wrap.cc:116: error: 'cl' was not declared in this scope
> sage/libs/mwrank/wrap.cc:117: error: 'vector' was not declared in this scope
> sage/libs/mwrank/wrap.cc:117: error: 'crs' was not declared in this scope
> sage/libs/mwrank/wrap.cc:118: error: 'Curve' was not declared in this scope
> sage/libs/mwrank/wrap.cc:118: error: 'cs' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'mw* mw_new(Curvedata*, int, int, int)':
> sage/libs/mwrank/wrap.cc:140: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc: In function 'void mw_del(mw*)':
> sage/libs/mwrank/wrap.cc:145: note: neither the destructor nor the
> class-specific operator delete will be called, even if they are
> declared when the class is defined.
> sage/libs/mwrank/wrap.cc: In function 'int mw_process(Curvedata*, mw*,
> const bigint*, const bigint*, const bigint*, int)':
> sage/libs/mwrank/wrap.cc:152: error: 'Point' was not declared in this scope
> sage/libs/mwrank/wrap.cc:152: error: expected `;' before 'P'
> sage/libs/mwrank/wrap.cc:153: error: 'P' was not declared in this scope
> sage/libs/mwrank/wrap.cc:155: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc:155: error: 'P' was not declared in this scope
> sage/libs/mwrank/wrap.cc: At global scope:
> sage/libs/mwrank/wrap.cc:159: error: expected ',' or '...' before '<' token
> sage/libs/mwrank/wrap.cc:159: error: ISO C++ forbids declaration of
> 'vector' with no type
> sage/libs/mwrank/wrap.cc: In function 'char* point_vector_to_str(int)':
> sage/libs/mwrank/wrap.cc:163: error: 'v' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'char* mw_getbasis(mw*)':
> sage/libs/mwrank/wrap.cc:174: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc: In function 'char* mw_regulator(mw*)':
> sage/libs/mwrank/wrap.cc:179: error: 'bigfloat' was not declared in this scope
> sage/libs/mwrank/wrap.cc:179: error: expected `;' before 'reg'
> sage/libs/mwrank/wrap.cc:181: error: 'reg' was not declared in this scope
> sage/libs/mwrank/wrap.cc: In function 'int mw_rank(mw*)':
> sage/libs/mwrank/wrap.cc:187: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc: In function 'int mw_saturate(mw*, bigint*,
> char**, long int, int)':
> sage/libs/mwrank/wrap.cc:194: error: 'vector' was not declared in this scope
> sage/libs/mwrank/wrap.cc:194: error: expected primary-expression before 'long'
> sage/libs/mwrank/wrap.cc:194: error: expected `;' before 'long'
> sage/libs/mwrank/wrap.cc:195: error: invalid use of undefined type 'struct mw'
> sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
> sage/libs/mwrank/wrap.cc:195: error: 'v' was not declared in this scope
> sage/libs/mwrank/wrap.cc: At global

[sage-support] Re: Sage-2.9

[Adam Getchell]

On Dec 18, 2007 10:27 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
> what happens if you type
>
>  sudo sage -br

I get the following errors during the process:

sage/libs/mwrank/wrap.cc: In function 'double
Curvedata_silverman_bound(const Curvedata*)':
sage/libs/mwrank/wrap.cc:81: error: 'silverman_bound' was not declared
in this scope
sage/libs/mwrank/wrap.cc: In function 'double
Curvedata_cps_bound(const Curvedata*)':
sage/libs/mwrank/wrap.cc:86: error: 'cps_bound' was not declared in this scope
sage/libs/mwrank/wrap.cc: In function 'double
Curvedata_height_constant(const Curvedata*)':
sage/libs/mwrank/wrap.cc:91: error: 'height_constant' was not declared
in this scope
sage/libs/mwrank/wrap.cc: In function 'char* Curvedata_getdiscr(Curvedata*)':
sage/libs/mwrank/wrap.cc:97: error: 'getdiscr' was not declared in this scope
sage/libs/mwrank/wrap.cc: In function 'char* Curvedata_conductor(Curvedata*)':
sage/libs/mwrank/wrap.cc:103: error: 'CurveRed' was not declared in this scope
sage/libs/mwrank/wrap.cc:103: error: expected `;' before 'E'
sage/libs/mwrank/wrap.cc:105: error: 'E' was not declared in this scope
sage/libs/mwrank/wrap.cc:105: error: 'getconductor' was not declared
in this scope
sage/libs/mwrank/wrap.cc: In function 'char*
Curvedata_isogeny_class(Curvedata*, int)':
sage/libs/mwrank/wrap.cc:113: error: 'CurveRed' was not declared in this scope
sage/libs/mwrank/wrap.cc:113: error: expected `;' before 'C'
sage/libs/mwrank/wrap.cc:114: error: 'C' was not declared in this scope
sage/libs/mwrank/wrap.cc:115: error: 'IsogenyClass' was not declared
in this scope
sage/libs/mwrank/wrap.cc:115: error: expected `;' before 'cl'
sage/libs/mwrank/wrap.cc:116: error: 'cl' was not declared in this scope
sage/libs/mwrank/wrap.cc:117: error: 'vector' was not declared in this scope
sage/libs/mwrank/wrap.cc:117: error: 'crs' was not declared in this scope
sage/libs/mwrank/wrap.cc:118: error: 'Curve' was not declared in this scope
sage/libs/mwrank/wrap.cc:118: error: 'cs' was not declared in this scope
sage/libs/mwrank/wrap.cc: In function 'mw* mw_new(Curvedata*, int, int, int)':
sage/libs/mwrank/wrap.cc:140: error: invalid use of undefined type 'struct mw'
sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
sage/libs/mwrank/wrap.cc: In function 'void mw_del(mw*)':
sage/libs/mwrank/wrap.cc:145: note: neither the destructor nor the
class-specific operator delete will be called, even if they are
declared when the class is defined.
sage/libs/mwrank/wrap.cc: In function 'int mw_process(Curvedata*, mw*,
const bigint*, const bigint*, const bigint*, int)':
sage/libs/mwrank/wrap.cc:152: error: 'Point' was not declared in this scope
sage/libs/mwrank/wrap.cc:152: error: expected `;' before 'P'
sage/libs/mwrank/wrap.cc:153: error: 'P' was not declared in this scope
sage/libs/mwrank/wrap.cc:155: error: invalid use of undefined type 'struct mw'
sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
sage/libs/mwrank/wrap.cc:155: error: 'P' was not declared in this scope
sage/libs/mwrank/wrap.cc: At global scope:
sage/libs/mwrank/wrap.cc:159: error: expected ',' or '...' before '<' token
sage/libs/mwrank/wrap.cc:159: error: ISO C++ forbids declaration of
'vector' with no type
sage/libs/mwrank/wrap.cc: In function 'char* point_vector_to_str(int)':
sage/libs/mwrank/wrap.cc:163: error: 'v' was not declared in this scope
sage/libs/mwrank/wrap.cc: In function 'char* mw_getbasis(mw*)':
sage/libs/mwrank/wrap.cc:174: error: invalid use of undefined type 'struct mw'
sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
sage/libs/mwrank/wrap.cc: In function 'char* mw_regulator(mw*)':
sage/libs/mwrank/wrap.cc:179: error: 'bigfloat' was not declared in this scope
sage/libs/mwrank/wrap.cc:179: error: expected `;' before 'reg'
sage/libs/mwrank/wrap.cc:181: error: 'reg' was not declared in this scope
sage/libs/mwrank/wrap.cc: In function 'int mw_rank(mw*)':
sage/libs/mwrank/wrap.cc:187: error: invalid use of undefined type 'struct mw'
sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
sage/libs/mwrank/wrap.cc: In function 'int mw_saturate(mw*, bigint*,
char**, long int, int)':
sage/libs/mwrank/wrap.cc:194: error: 'vector' was not declared in this scope
sage/libs/mwrank/wrap.cc:194: error: expected primary-expression before 'long'
sage/libs/mwrank/wrap.cc:194: error: expected `;' before 'long'
sage/libs/mwrank/wrap.cc:195: error: invalid use of undefined type 'struct mw'
sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
sage/libs/mwrank/wrap.cc:195: error: 'v' was not declared in this scope
sage/libs/mwrank/wrap.cc: At global scope:
sage/libs/mwrank/wrap.cc:202: error: 'bigfloat' does not name a type
sage/libs/mwrank/wrap.cc: In function 'void mw_search(mw*, char*, int, int)':
sage/libs/mwrank/wrap.cc:213: error: invalid use of undefined type 'struct mw'
sage/libs/mwrank/wrap.h:73: error: forward declaration of 'struct mw'
sage/libs/mwrank/wrap.cc:213:

[sage-support] Re: Sage-2.9

[davedo2]

Michael,

You had advised me to try the following command to adjust the laptop's
performance:

/usr/bin/cpufreq-selector -g performance

However, cpufreq-selector doesn't appear to be available for kubuntu
7.10, at least I couldn't find it with either Adept or apt-get. I did
install everything that related to cpufreq and found what seemed the
closest, cpufreq-set. I blindly ran that with both the -g &
performance arguments (although looking at the man later performance
doesn't seem to apply.)

In any event, the install then creeped slowly, but surely, to a
successful completion. SAGE loads properly as does the notebook and
the long test ran with no errors found.

Thanks much for your help...Dave

On Dec 18, 2:02 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On Dec 18, 10:36 pm, davedo2 <[EMAIL PROTECTED]> wrote:
>
> >  Willam,
>
> Hi,
>
>
>
> >  The day after I had done a successful install from source of 2.8.15
> > on
> >  my laptop (which is running kubuntu 7.10) the 2.9 release was
> >  announced.
>
> It is a blessing and a curse to do about a release a week :)
>
>
>
> > OK, first I tried sage -upgrade, but after a LONG run that
> >  failed with several error messages that regretfully I didn't capture.
> >  I then downloaded the source for 2.9 and after removing the remnants
> >  of the failed upgrade I tried the untar & make process. After another
> >  longish session the process aborted abruptly by shutting down the
> > PC?!
> >  I thought I might have had a bad download so I tried again from
> >  another PC, transfeerred the tar to the laptop & tried again - same
> >  result.
>
> >  I don't have a spot to post the full install log, but the last few
> >  lines, and the result if I attempt to start SAGE from what was built,
> >  is this:
>
> >  Last view lines of install.log
> >  ~~
> >  make dmmcase0 pre=d ta=T tb=N muladd=1 lat=1 loopO=JIK M=52 N=52 K=52
> >  mb=52 nb=5
> >  2 kb=52 mu=4 nu=1 ku=52 lda=52 ldb=52 ldc=0 lda2=52 ldb2=52 ldc2=0
> >  pfA=0
> >  csA=1 c
> >  sB=1 csC=1 alpha=1 beta=1 moves="" cleanup=1 mmrout="dmm0.c"
> > SMC="gcc"
> >  SMCFLAGS=
> >  "-fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -m32"
> >  DMC="gcc" DMC
> >  FLAGS="-fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -
> >  m32"
> >  casnam=
> >  res/dJIKmmTN52_52x52x52_52x52x0_4x1x52_a1_b1_1x1_1_IC
> >  make[7]: Entering directory
> >  `/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS
> >  -build/tune/blas/gemm'
> >  rm -f dfc.o dmm.o
> >  gcc -DL2SIZE=4194304
> >  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build
> >  /include
> >  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/
> >  ATLA
> >  S//include
> >  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/AT
> >  S//include
> >  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/AT
> >  LAS//include/contrib -DAdd__ -DF77_INTEGER=int -DStringSunStyle
> >  -DATL_OS_Linux -
> >  DATL_ARCH_HAMMER -DATL_CPUMHZ=2000 -DATL_SSE2 -DATL_SSE1 -DATL_3DNow
> >  -DATL_GAS_x
> >  8632  -fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -
> > m32
> >  -DdREAL -
> >  DtranAT -DtranBN \
>
> ATLAS failed to compile for you. It is no surprise that starting Sage
> afterwards fails. It isn't clear from the excerpt from the logs *why*
> it failed, so please post the couple missing lines from there until
> the end. Main potential culprit is power management in your case.
> Turning that off will *probably* solve the problem.
>
> Cheers,
>
> Michael
>
> >  ~~~
> >  Error msg upon starting SAGE
> >  ~~
> >  [EMAIL PROTECTED]:~/sage-2.9$ sage
>
> > --
> >  | SAGE Version 2.9, Release Date: 2007-12-16
> > |
> >  | Type notebook() for the GUI, and license() for information.
> > |
>
> > --
> >  Traceback (most recent call last):
> >   File "/home/davedo/sage-2.9/local/bin/sage-ipython", line 10, in
> >  
> > import IPython
> >  ImportError: No module named IPython
> >  ~
> >  [EMAIL PROTECTED]:~$
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 18, 11:08 pm, Paul Zimmermann <[EMAIL PROTECTED]> wrote:
> > ATLAS failed to compile for you. It is no surprise that starting Sage
> > afterwards fails. It isn't clear from the excerpt from the logs *why*
> > it failed, so please post the couple missing lines from there until
> > the end. Main potential culprit is power management in your case.
> > Turning that off will *probably* solve the problem.
>
> by the way, I noticed while compiling sage-2.9 from source on my laptop
> (Pentium M) that ATLAS ran MANY tuning tests, which did take VERY long.
> Wouldn't it be possible to use some default machine parameters, like GMP does?
>

Hello Paul,

#1547, William experienced that one, too. ATLAS has pretuned
parameters for a lot of CPUs, but not that particular model.I am
looking into this, but haven't had time to fix this yet. If anybody
else wants to figure it out feel free to do so, my feelings won't get
hurt :). Could you provide the output from /proc/cpuinfo?

> Cheers,
> Paul Zimmermann

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Paul Zimmermann]

> ATLAS failed to compile for you. It is no surprise that starting Sage
> afterwards fails. It isn't clear from the excerpt from the logs *why*
> it failed, so please post the couple missing lines from there until
> the end. Main potential culprit is power management in your case.
> Turning that off will *probably* solve the problem.

by the way, I noticed while compiling sage-2.9 from source on my laptop
(Pentium M) that ATLAS ran MANY tuning tests, which did take VERY long.
Wouldn't it be possible to use some default machine parameters, like GMP does?

Cheers,
Paul Zimmermann

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 18, 10:36 pm, davedo2 <[EMAIL PROTECTED]> wrote:
>  Willam,

Hi,

>
>  The day after I had done a successful install from source of 2.8.15
> on
>  my laptop (which is running kubuntu 7.10) the 2.9 release was
>  announced.

It is a blessing and a curse to do about a release a week :)

> OK, first I tried sage -upgrade, but after a LONG run that
>  failed with several error messages that regretfully I didn't capture.
>  I then downloaded the source for 2.9 and after removing the remnants
>  of the failed upgrade I tried the untar & make process. After another
>  longish session the process aborted abruptly by shutting down the
> PC?!
>  I thought I might have had a bad download so I tried again from
>  another PC, transfeerred the tar to the laptop & tried again - same
>  result.
>
>  I don't have a spot to post the full install log, but the last few
>  lines, and the result if I attempt to start SAGE from what was built,
>  is this:
>
>  Last view lines of install.log
>  ~~
>  make dmmcase0 pre=d ta=T tb=N muladd=1 lat=1 loopO=JIK M=52 N=52 K=52
>  mb=52 nb=5
>  2 kb=52 mu=4 nu=1 ku=52 lda=52 ldb=52 ldc=0 lda2=52 ldb2=52 ldc2=0
>  pfA=0
>  csA=1 c
>  sB=1 csC=1 alpha=1 beta=1 moves="" cleanup=1 mmrout="dmm0.c"
> SMC="gcc"
>  SMCFLAGS=
>  "-fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -m32"
>  DMC="gcc" DMC
>  FLAGS="-fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -
>  m32"
>  casnam=
>  res/dJIKmmTN52_52x52x52_52x52x0_4x1x52_a1_b1_1x1_1_IC
>  make[7]: Entering directory
>  `/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS
>  -build/tune/blas/gemm'
>  rm -f dfc.o dmm.o
>  gcc -DL2SIZE=4194304
>  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build
>  /include
>  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/
>  ATLA
>  S//include
>  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/AT
>  S//include
>  -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/AT
>  LAS//include/contrib -DAdd__ -DF77_INTEGER=int -DStringSunStyle
>  -DATL_OS_Linux -
>  DATL_ARCH_HAMMER -DATL_CPUMHZ=2000 -DATL_SSE2 -DATL_SSE1 -DATL_3DNow
>  -DATL_GAS_x
>  8632  -fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -
> m32
>  -DdREAL -
>  DtranAT -DtranBN \

ATLAS failed to compile for you. It is no surprise that starting Sage
afterwards fails. It isn't clear from the excerpt from the logs *why*
it failed, so please post the couple missing lines from there until
the end. Main potential culprit is power management in your case.
Turning that off will *probably* solve the problem.

Cheers,

Michael

>  ~~~
>  Error msg upon starting SAGE
>  ~~
>  [EMAIL PROTECTED]:~/sage-2.9$ sage
>
> --
>  | SAGE Version 2.9, Release Date: 2007-12-16
> |
>  | Type notebook() for the GUI, and license() for information.
> |
>
> --
>  Traceback (most recent call last):
>   File "/home/davedo/sage-2.9/local/bin/sage-ipython", line 10, in
>  
> import IPython
>  ImportError: No module named IPython
>  ~
>  [EMAIL PROTECTED]:~$
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[davedo2]

 Willam,

 The day after I had done a successful install from source of 2.8.15
on
 my laptop (which is running kubuntu 7.10) the 2.9 release was
 announced. OK, first I tried sage -upgrade, but after a LONG run that
 failed with several error messages that regretfully I didn't capture.
 I then downloaded the source for 2.9 and after removing the remnants
 of the failed upgrade I tried the untar & make process. After another
 longish session the process aborted abruptly by shutting down the
PC?!
 I thought I might have had a bad download so I tried again from
 another PC, transfeerred the tar to the laptop & tried again - same
 result.

 I don't have a spot to post the full install log, but the last few
 lines, and the result if I attempt to start SAGE from what was built,
 is this:

 Last view lines of install.log
 ~~
 make dmmcase0 pre=d ta=T tb=N muladd=1 lat=1 loopO=JIK M=52 N=52 K=52
 mb=52 nb=5
 2 kb=52 mu=4 nu=1 ku=52 lda=52 ldb=52 ldc=0 lda2=52 ldb2=52 ldc2=0
 pfA=0
 csA=1 c
 sB=1 csC=1 alpha=1 beta=1 moves="" cleanup=1 mmrout="dmm0.c"
SMC="gcc"
 SMCFLAGS=
 "-fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -m32"
 DMC="gcc" DMC
 FLAGS="-fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -
 m32"
 casnam=
 res/dJIKmmTN52_52x52x52_52x52x0_4x1x52_a1_b1_1x1_1_IC
 make[7]: Entering directory
 `/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS
 -build/tune/blas/gemm'
 rm -f dfc.o dmm.o
 gcc -DL2SIZE=4194304
 -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build
 /include
 -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/
 ATLA
 S//include
 -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/AT
 S//include
 -I/home/davedo/sage-2.9/spkg/build/atlas-3.8.p6/ATLAS-build/../src/AT
 LAS//include/contrib -DAdd__ -DF77_INTEGER=int -DStringSunStyle
 -DATL_OS_Linux -
 DATL_ARCH_HAMMER -DATL_CPUMHZ=2000 -DATL_SSE2 -DATL_SSE1 -DATL_3DNow
 -DATL_GAS_x
 8632  -fomit-frame-pointer -mfpmath=387 -O2 -falign-loops=4 -fPIC -
m32
 -DdREAL -
 DtranAT -DtranBN \
 ~~~
 Error msg upon starting SAGE
 ~~
 [EMAIL PROTECTED]:~/sage-2.9$ sage
 
--
 | SAGE Version 2.9, Release Date: 2007-12-16
|
 | Type notebook() for the GUI, and license() for information.
|
 
--
 Traceback (most recent call last):
  File "/home/davedo/sage-2.9/local/bin/sage-ipython", line 10, in
 
import IPython
 ImportError: No module named IPython
 ~
 [EMAIL PROTECTED]:~$

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[William Stein]

what happens if you type

 sudo sage -br

then try sage -notebook again

- William

(Sent from my iPhone.)

On Dec 18, 2007, at 10:35 AM, "Adam Getchell"  
<[EMAIL PROTECTED]> wrote:

>
> Did sage -upgrade on 32-bit VMWare image. Upgrade works, but  
> notebook doesn't:
>
> [EMAIL PROTECTED]:~$ sudo sage -notebook
> --
> | SAGE Version 2.9, Release Date: 2007-12-16 |
> | Type notebook() for the GUI, and license() for information.|
> --
>
> Please wait while the SAGE Notebook server starts...
> Traceback (most recent call last):
>  File "/usr/local/sage/local/bin/sage-notebook", line 9, in 
>from sage.server.notebook.all import notebook
> ImportError: No module named sage.server.notebook.all
>
> Error message seems pretty clear. There isn't a
> /usr/local/sage/local/bin/notebook.py file, if there should be. How
> would I determine where $SAGE_ROOT is?
>
> I've pretty extensively modified this VM (Xubuntu, other stuff) so I'm
> hoping it's an easy fix ...
>
> Thanks!
>
> On Dec 17, 2007 8:05 AM, mabshoff
> <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> On Dec 17, 2:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi Kiran,
>>
>>> I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
>>> upgrade dies pretty definitively at PolyBoRi. As far as I can  
>>> tell, on
>>> the first file it is throwing lots of compile errors of the form
>>>
>>> /tmp/cciylcHI.s:17647: Error: suffix or operands invalid for `push'
>>> /tmp/cciylcHI.s:17697: Error: suffix or operands invalid for `pop'
>>>
>>> I'm guessing/hoping this is probably some easy fix on my end. Any
>>> suggestions?
>>
>> That is a bashism that was supposedly fixed by Burcin. It might have
>> snuck back into the latest spkg. I will investigate this. rlm created
>> #1553 for this.
>>
>>> Kiran
>>
>> Cheers,
>>
>> Michael
>>
>>>
>>
>
>
>
> -- 
> "Invincibility is in oneself, vulnerability in the opponent." -- Sun  
> Tzu
>
> >

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Adam Getchell]

Did sage -upgrade on 32-bit VMWare image. Upgrade works, but notebook doesn't:

[EMAIL PROTECTED]:~$ sudo sage -notebook
--
| SAGE Version 2.9, Release Date: 2007-12-16 |
| Type notebook() for the GUI, and license() for information.|
--

Please wait while the SAGE Notebook server starts...
Traceback (most recent call last):
  File "/usr/local/sage/local/bin/sage-notebook", line 9, in 
from sage.server.notebook.all import notebook
ImportError: No module named sage.server.notebook.all

Error message seems pretty clear. There isn't a
/usr/local/sage/local/bin/notebook.py file, if there should be. How
would I determine where $SAGE_ROOT is?

I've pretty extensively modified this VM (Xubuntu, other stuff) so I'm
hoping it's an easy fix ...

Thanks!

On Dec 17, 2007 8:05 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 17, 2:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
>
> Hi Kiran,
>
> > I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
> > upgrade dies pretty definitively at PolyBoRi. As far as I can tell, on
> > the first file it is throwing lots of compile errors of the form
> >
> > /tmp/cciylcHI.s:17647: Error: suffix or operands invalid for `push'
> > /tmp/cciylcHI.s:17697: Error: suffix or operands invalid for `pop'
> >
> > I'm guessing/hoping this is probably some easy fix on my end. Any
> > suggestions?
>
> That is a bashism that was supposedly fixed by Burcin. It might have
> snuck back into the latest spkg. I will investigate this. rlm created
> #1553 for this.
>
> > Kiran
>
> Cheers,
>
> Michael
>
> >
>



-- 
"Invincibility is in oneself, vulnerability in the opponent." -- Sun Tzu

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 17, 2:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:


Hi Kiran,

> I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
> upgrade dies pretty definitively at PolyBoRi. As far as I can tell, on
> the first file it is throwing lots of compile errors of the form
>
> /tmp/cciylcHI.s:17647: Error: suffix or operands invalid for `push'
> /tmp/cciylcHI.s:17697: Error: suffix or operands invalid for `pop'
>
> I'm guessing/hoping this is probably some easy fix on my end. Any
> suggestions?

That is a bashism that was supposedly fixed by Burcin. It might have
snuck back into the latest spkg. I will investigate this. rlm created
#1553 for this.

> Kiran

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Jaap Spies]

mabshoff wrote:
> 
> 
> On Dec 17, 1:50 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>> On Dec 17, 2007 7:31 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>>
>>

[...]
 # QUESTION: Upgrading Sage went fine, but now the banner still shows
 the old version. How can I fix this?
 # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
 hg_scripts.commit().
>>> More simple I did:
>>> [EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
>>> --
>>> | SAGE Version rc4, Release Date: 2007-12-16 |
>>> | Type notebook() for the GUI, and license() for information.|
>>> --
>>> sage: hg_scripts.pull()
>> That worked! Thanks:-) Should I add this to the FAQ?
> 
> It is more or less the same solution I posted, just from inside sage.
> But feel free to add it to that existing FAQ entry as an alternative
> methode.
> 

In the quotes you gave there is hg_scripts.merge() and hg_script.commit(),
from inside sage too :)

Jaap


--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[[EMAIL PROTECTED]]

I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
upgrade dies pretty definitively at PolyBoRi. As far as I can tell, on
the first file it is throwing lots of compile errors of the form

/tmp/cciylcHI.s:17647: Error: suffix or operands invalid for `push'
/tmp/cciylcHI.s:17697: Error: suffix or operands invalid for `pop'

I'm guessing/hoping this is probably some easy fix on my end. Any
suggestions?

Kiran

On Dec 16, 11:04 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Sage 2.9 has been released. It is available at
>
>http://sagemath.org/download.html
>
> This is a *major* new release, with a huge number of tickets
> closed, and the additional of both R and the ATLAS BLAS
> as standard packages.
>
> If you're an *expert* user or just brave, do
>
>sage -upgrade
>
> but this may yield your sage temporarily unusable -- if that does happen,
> do email sage-support.
>
> If you're a beginner install from source or wait for new
> binaries to be posted in a few days (or less).
>
> ---
>
> The following people contributed this release:
>
>  * Michael Abshoff
>  * Martin Albrecht
>  * Robert Bradshaw
>  * Tom Boothby
>  * Ondrej Certik
>  * Craig Citro
>  * F. Clark
>  * John Cremona
>  * Alyson Deines
>  * Burcin Erocal
>  * Jan Groenewald
>  * David Harvey
>  * Mike Hansen
>  * Josh Kantor
>  * Robert Miller
>  * Bobby Moretti
>  * Rich Morin
>  * Bill Page
>  * Willem Jan Palenstijn
>  * Yi Qiang
>  * David Roe
>  * William Stein
>  * Carl Witty
>  * Paul Zimmermann
>
> Cheers,
>
> Michael Abshoff (release chair), William Stein
>
> * Major Features, New Spkgs and Bugfixes
>
> We achieved most of the goals we set ourselves for 2.9. The major
> changes compared to 2.8.15 are:
>
>  * Integration of PolyBoRi
>  * Integration of ATLAS BLAS/Lapack on non-OSX
>  * Integration of R 2.6.1 and rpy
>  * Update to FLINT 1.02
>  * Update to Symmetrica 2.0
>  * Much faster permutation arithmatic
>  * Very fast rubik's cube solvers
>  * Many build fixes applied and many bugs squashed
>
> We closed a total of 110 tickets, for details see below or our
> tracker at
>
> http://www.sagetrac.org/sage_trac/query?status=closed&milestone=sage-2.9
>
> * Known Issues with 2.9
>
> #1137: Import gd fails to import on OSX 10.4 ppc. Any attempt
>to fix this breaks other applications on different OSX
>flavors. We hope to fix this in 2.9.1.
> #1497: ATLAS fails to build on FC7, Dual core [known ATLAS
>issue with workaround: disable power management]
>
> * Upcoming Releases
>
> The following releases are planned for the rest of the year:
>
>  * 2.9.1: chaired by Robert Miller, bug fixes, release
>   planned about a week from now
>  * 2.9.2: chaired by Michael Abshoff, bug fixes, release
>   planned about two weeks from now
>
> 2.9.2 will be the release we plan to distribute on DVD at the AMS
> meeting, so we are shooting hard for an excellent release.
>
> * Doctesting Coverage
>
> For 2.9:
>
> Overall weighted coverage score:  35.3%
> Total number of functions:  17947
>
> Compared to 2.8.15 this is an increase by 0.5%.
>
> * About Sage (http://www.sagemath.org)
>
> Sage is developed by volunteers and combines 71 open source packages.
> It is available for download from sagemath.org and its mirrors in
> source or binary form. If you have any questions and/or problems
> please report them to the google groups sage-devel, sage-support,
> sage-forum or sage-newbie. You can also drop by in #sage-devel in
> freenode.
>
> * Closed Tickets:
>
> Merged in rc3:
>
> #1529: William Stein: update install_scripts to also install R script.
> #1530: William Stein: building tut.tex is currently broken
> #1531: Michael Abshoff: fix doctest failure sage/calculus/calculus.py
> #1532: Josh Kantor; Michael Abshoff: Error out with intelligent
>message if ATLAS tune failed
>
> Without tickets:
>
> William Stein: update libpng.spkg
> William Stein: don't let "sage -ba" start sage
> William Stein: link libcsage.so against atlas on non-OSX
> William Stein: link IML against atlas on non-OSX
> Willaim Stein, Michael Abshoff: Various doctest fixes
> Michael Abshoff: link LinBox against atlas on non-OSX
> Michael Abshoff: remove forced check from FLINT.spkg
>
> Merged in rc1/2:
>
> #1258: Willem Jan Palenstijn, Robert Miller: additions and changes
>to linear_codes
> #1457: William Stein: "BUG: Rational.__pow__ called on a non-Rational"
> #1464: Robert Miller: binary code canonical labels & automorphism
>group generators
> #1503: William Stein: formal function calls don't coerce correctly to
>Mathematica
> #1511: Robert Bradshaw: Export 3d objects in jmol format
> #1527: William Stein: doctest R with "import rpy"
> #1528: William Stein: make "sage -R" run R.
>
> Merged in rc0:
>
> #444: Robert Bradshaw: solve the rubik's cube fast!
> #553: Mike Hansen, William Stein: calling of symbolic expressions is
>   sometimes ridiculous
> #1077: Yi Q

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 17, 1:41 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> After a fresh 2.9 build on
> Dual-Core AMD Opteron(tm) Processor 2220
>
> --testall  just produxed this:
>
> The following tests failed:
>
> sage -t  devel/sage-main/sage/calculus/calculus.py
> Total time for all tests: 1424.9 seconds
> Please see /home/jec/sage-2.9/tmp/test.log for the complete log from this 
> test.
>
> sage -t  devel/sage-main/sage/calculus/calculus.py
> **
> File "calculus.py", line 2460:
> sage: v.find_root(0, 0.002)
> Expected:
> 0.0015403270679114178
> Got:
> 0.0015403270679114176
> **
> File "calculus.py", line 2473:
> sage: a.find_root(0,0.002)
> Expected:
> 0.00041105140493493411
> Got:
> 0.00041105140493493417
> **
> 1 items had failures:
>2 of  16 in __main__.example_50
> ***Test Failed*** 2 failures.
> For whitespace errors, see the file .doctest_calculus.py
>
> John

Hi John,

this is now #1548 and easy enough to fix. Thanks for the report.

Cheers,

Michael


>
> On 17/12/2007, mabshoff
>
>
>
> <[EMAIL PROTECTED]> wrote:
>
> > On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > > On Dec 16, 2007 11:19 PM, mabshoff
>
> > > <[EMAIL PROTECTED]> wrote:
>
> > > > Hello,
>
> > > > I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
> > > > release on sage.math. While -long passed with flying colors, -optional
> > > > had some failures in tut.tex since I didn't install some optional GAP
> > > > database. But there are also some problems with maxima, which might
>
> > > Maybe
> > > database_gap-4.4.10
> > > (There is also a newer version of this BTW.)
>
> > Ok, I will install that db next time I test. At least the first two
> > failure were related to some printing changes in 2.9:
>
> > File "tut.py", line 3390:
> > : G
> > Expected:
> > Group([ (1,2,3)(4,5), (3,4) ])
> > Got:
> > Group( [ (1,2,3)(4,5), (3,4) ] )
> > **
> > File "tut.py", line 3392:
> > : G.Center()
> > Expected:
> > Group(())
> > Got:
> > Group( () )
>
> > Those are easy enough to fix.
>
> > > > just be fallout from the GAP failure. I will investigate, but it seems
>
> > > I don't think we have (at this point) any functions which mix maxima
> > > and GAP code.
> > > (I wish there were and would be happy to be corrected!)
>
> > Nope, I looked and the maxima failures were all in plotting code, most
> > likely related to the fact that I did run the test of an ssh connect
> > without exporting X over ssh at the same time.
>
> > > I did a sage -upgrade to 2.9 and had no serious problems but just notices 
> > > that
> > > the startup banner is missing "2.9". Is that just me?
>
> > I think William reported something similar. To fix it see the faq,
> > specifically:
>
> > # QUESTION: Upgrading Sage went fine, but now the banner still shows
> > the old version. How can I fix this?
> > # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> > hg_scripts.commit().
>
> > > [EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
> > > --
> > > | SAGE Version rc4, Release Date: 2007-12-16 |
> > > | Type notebook() for the GUI, and license() for information.|
> > > --
>
> > > sage: version()
> > > 'SAGE Version 2.9, Release Date: 2007-12-16'
>
> > > > that we are in reasonably good shape [William had feared that loads of
> > > > things would go *boom*].
>
> > > > Cheers,
>
> > > > Michael
>
> > Cheers,
>
> > Michael
>
> --
> John Cremona
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 17, 1:50 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> On Dec 17, 2007 7:31 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > mabshoff wrote:
>
> > > On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> > >> I did a sage -upgrade to 2.9 and had no serious problems but just 
> > >> notices that
> > >> the startup banner is missing "2.9". Is that just me?
>
> > > I think William reported something similar. To fix it see the faq,
> > > specifically:
>
> > > # QUESTION: Upgrading Sage went fine, but now the banner still shows
> > > the old version. How can I fix this?
> > > # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> > > hg_scripts.commit().
>
> > More simple I did:
>
> > [EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
> > --
> > | SAGE Version rc4, Release Date: 2007-12-16 |
> > | Type notebook() for the GUI, and license() for information.|
> > --
>
> > sage: hg_scripts.pull()
>
> That worked! Thanks:-) Should I add this to the FAQ?

It is more or less the same solution I posted, just from inside sage.
But feel free to add it to that existing FAQ entry as an alternative
methode.

Cheers,

Michael

> > cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg status
> > cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg status
> > cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg pull 
> > -uhttp://www.sagemath.org/hg/scripts-main
> > pulling fromhttp://www.sagemath.org/hg/scripts-main
> > searching for changes
> > adding changesets
> > adding manifests
> > adding file changes
> > added 1 changesets with 1 changes to 1 files
> > 1 files updated, 0 files merged, 0 files removed, 0 files unresolved
> > If it says use 'hg merge' above, then you should
> > type hg_scripts.merge().
>
> > sage:
> > Exiting SAGE (CPU time 0m0.02s, Wall time 0m28.11s).
> > [EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
> > --
> > | SAGE Version 2.9, Release Date: 2007-12-16 |
> > | Type notebook() for the GUI, and license() for information.|
> > --
>
> > Jaap
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[David Joyner]

On Dec 17, 2007 7:31 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> mabshoff wrote:
> >
> >
> > On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> >
> >> I did a sage -upgrade to 2.9 and had no serious problems but just notices 
> >> that
> >> the startup banner is missing "2.9". Is that just me?
> >
> > I think William reported something similar. To fix it see the faq,
> > specifically:
> >
> > # QUESTION: Upgrading Sage went fine, but now the banner still shows
> > the old version. How can I fix this?
> > # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> > hg_scripts.commit().
> >
>
> More simple I did:
>
> [EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
> --
> | SAGE Version rc4, Release Date: 2007-12-16 |
> | Type notebook() for the GUI, and license() for information.|
> --
>
>
> sage: hg_scripts.pull()


That worked! Thanks:-) Should I add this to the FAQ?



> cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg status
> cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg status
> cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg pull -u 
> http://www.sagemath.org/hg/scripts-main
> pulling from http://www.sagemath.org/hg/scripts-main
> searching for changes
> adding changesets
> adding manifests
> adding file changes
> added 1 changesets with 1 changes to 1 files
> 1 files updated, 0 files merged, 0 files removed, 0 files unresolved
> If it says use 'hg merge' above, then you should
> type hg_scripts.merge().
>
> sage:
> Exiting SAGE (CPU time 0m0.02s, Wall time 0m28.11s).
> [EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
> --
> | SAGE Version 2.9, Release Date: 2007-12-16 |
> | Type notebook() for the GUI, and license() for information.|
> --
>
>
>
> Jaap
>
>
>
> >
>

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Jaap Spies]

mabshoff wrote:
> 
> 
> On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:

> 
>> I did a sage -upgrade to 2.9 and had no serious problems but just notices 
>> that
>> the startup banner is missing "2.9". Is that just me?
> 
> I think William reported something similar. To fix it see the faq,
> specifically:
> 
> # QUESTION: Upgrading Sage went fine, but now the banner still shows
> the old version. How can I fix this?
> # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> hg_scripts.commit().
> 

More simple I did:

[EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
--
| SAGE Version rc4, Release Date: 2007-12-16 |
| Type notebook() for the GUI, and license() for information.|
--


sage: hg_scripts.pull()
cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg status
cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg status
cd "/home/jaap/downloads/sage-2.9.rc4/local/bin" && hg pull -u 
http://www.sagemath.org/hg/scripts-main
pulling from http://www.sagemath.org/hg/scripts-main
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
If it says use 'hg merge' above, then you should
type hg_scripts.merge().

sage:
Exiting SAGE (CPU time 0m0.02s, Wall time 0m28.11s).
[EMAIL PROTECTED] sage-2.9.rc4]$ ./sage
--
| SAGE Version 2.9, Release Date: 2007-12-16 |
| Type notebook() for the GUI, and license() for information.|
--



Jaap


--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[John Cremona]

After a fresh 2.9 build on
Dual-Core AMD Opteron(tm) Processor 2220

--testall  just produxed this:

The following tests failed:


sage -t  devel/sage-main/sage/calculus/calculus.py
Total time for all tests: 1424.9 seconds
Please see /home/jec/sage-2.9/tmp/test.log for the complete log from this test.


sage -t  devel/sage-main/sage/calculus/calculus.py
**
File "calculus.py", line 2460:
sage: v.find_root(0, 0.002)
Expected:
0.0015403270679114178
Got:
0.0015403270679114176
**
File "calculus.py", line 2473:
sage: a.find_root(0,0.002)
Expected:
0.00041105140493493411
Got:
0.00041105140493493417
**
1 items had failures:
   2 of  16 in __main__.example_50
***Test Failed*** 2 failures.
For whitespace errors, see the file .doctest_calculus.py

John


On 17/12/2007, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > On Dec 16, 2007 11:19 PM, mabshoff
> >
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Hello,
> >
> > > I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
> > > release on sage.math. While -long passed with flying colors, -optional
> > > had some failures in tut.tex since I didn't install some optional GAP
> > > database. But there are also some problems with maxima, which might
> >
> > Maybe
> > database_gap-4.4.10
> > (There is also a newer version of this BTW.)
>
> Ok, I will install that db next time I test. At least the first two
> failure were related to some printing changes in 2.9:
>
> File "tut.py", line 3390:
> : G
> Expected:
> Group([ (1,2,3)(4,5), (3,4) ])
> Got:
> Group( [ (1,2,3)(4,5), (3,4) ] )
> **
> File "tut.py", line 3392:
> : G.Center()
> Expected:
> Group(())
> Got:
> Group( () )
>
> Those are easy enough to fix.
>
> > > just be fallout from the GAP failure. I will investigate, but it seems
> >
> > I don't think we have (at this point) any functions which mix maxima
> > and GAP code.
> > (I wish there were and would be happy to be corrected!)
>
> Nope, I looked and the maxima failures were all in plotting code, most
> likely related to the fact that I did run the test of an ssh connect
> without exporting X over ssh at the same time.
>
> > I did a sage -upgrade to 2.9 and had no serious problems but just notices 
> > that
> > the startup banner is missing "2.9". Is that just me?
>
> I think William reported something similar. To fix it see the faq,
> specifically:
>
> # QUESTION: Upgrading Sage went fine, but now the banner still shows
> the old version. How can I fix this?
> # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> hg_scripts.commit().
>
> > [EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
> > --
> > | SAGE Version rc4, Release Date: 2007-12-16 |
> > | Type notebook() for the GUI, and license() for information.|
> > --
> >
> > sage: version()
> > 'SAGE Version 2.9, Release Date: 2007-12-16'
> >
> > > that we are in reasonably good shape [William had feared that loads of
> > > things would go *boom*].
> >
> > > Cheers,
> >
> > > Michael
>
> Cheers,
>
> Michael
> >
>


-- 
John Cremona

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[David Joyner]

On Dec 17, 2007 6:56 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > On Dec 16, 2007 11:19 PM, mabshoff
> >
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Hello,
> >
> > > I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
> > > release on sage.math. While -long passed with flying colors, -optional
> > > had some failures in tut.tex since I didn't install some optional GAP
> > > database. But there are also some problems with maxima, which might
> >
> > Maybe
> > database_gap-4.4.10
> > (There is also a newer version of this BTW.)
>
> Ok, I will install that db next time I test. At least the first two
> failure were related to some printing changes in 2.9:
>
> File "tut.py", line 3390:
> : G
> Expected:
> Group([ (1,2,3)(4,5), (3,4) ])
> Got:
> Group( [ (1,2,3)(4,5), (3,4) ] )
> **
> File "tut.py", line 3392:
> : G.Center()
> Expected:
> Group(())
> Got:
> Group( () )
>
> Those are easy enough to fix.
>
> > > just be fallout from the GAP failure. I will investigate, but it seems
> >
> > I don't think we have (at this point) any functions which mix maxima
> > and GAP code.
> > (I wish there were and would be happy to be corrected!)
>
> Nope, I looked and the maxima failures were all in plotting code, most
> likely related to the fact that I did run the test of an ssh connect
> without exporting X over ssh at the same time.
>
> > I did a sage -upgrade to 2.9 and had no serious problems but just notices 
> > that
> > the startup banner is missing "2.9". Is that just me?
>
> I think William reported something similar. To fix it see the faq,
> specifically:
>
> # QUESTION: Upgrading Sage went fine, but now the banner still shows
> the old version. How can I fix this?
> # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> hg_scripts.commit().


That had no effect. This is on a 64bit ubuntu machine.

sage: hg_scripts.merge()
cd "/home/wdj/wdj/sagefiles/sage-2.9.alpha5/local/bin" && hg merge
abort: there is nothing to merge
sage: hg_scripts.commit()
cd "/home/wdj/wdj/sagefiles/sage-2.9.alpha5/local/bin" && hg diff  | less
cd "/home/wdj/wdj/sagefiles/sage-2.9.alpha5/local/bin" && hg commit
nothing changed
sage:
Exiting SAGE (CPU time 0m1.79s, Wall time 57m35.15s).
Exiting spawned Maxima process.
[EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
--
| SAGE Version rc4, Release Date: 2007-12-16 |
| Type notebook() for the GUI, and license() for information.|
--


>
>
> > [EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
> > --
> > | SAGE Version rc4, Release Date: 2007-12-16 |
> > | Type notebook() for the GUI, and license() for information.|
> > --
> >
> > sage: version()
> > 'SAGE Version 2.9, Release Date: 2007-12-16'
> >
> > > that we are in reasonably good shape [William had feared that loads of
> > > things would go *boom*].
> >
> > > Cheers,
> >
> > > Michael
>
> Cheers,
>
> Michael
> >
>

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> On Dec 16, 2007 11:19 PM, mabshoff
>
> <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
> > release on sage.math. While -long passed with flying colors, -optional
> > had some failures in tut.tex since I didn't install some optional GAP
> > database. But there are also some problems with maxima, which might
>
> Maybe
> database_gap-4.4.10
> (There is also a newer version of this BTW.)

Ok, I will install that db next time I test. At least the first two
failure were related to some printing changes in 2.9:

File "tut.py", line 3390:
: G
Expected:
Group([ (1,2,3)(4,5), (3,4) ])
Got:
Group( [ (1,2,3)(4,5), (3,4) ] )
**
File "tut.py", line 3392:
: G.Center()
Expected:
Group(())
Got:
Group( () )

Those are easy enough to fix.

> > just be fallout from the GAP failure. I will investigate, but it seems
>
> I don't think we have (at this point) any functions which mix maxima
> and GAP code.
> (I wish there were and would be happy to be corrected!)

Nope, I looked and the maxima failures were all in plotting code, most
likely related to the fact that I did run the test of an ssh connect
without exporting X over ssh at the same time.

> I did a sage -upgrade to 2.9 and had no serious problems but just notices that
> the startup banner is missing "2.9". Is that just me?

I think William reported something similar. To fix it see the faq,
specifically:

# QUESTION: Upgrading Sage went fine, but now the banner still shows
the old version. How can I fix this?
# ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
hg_scripts.commit().

> [EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
> --
> | SAGE Version rc4, Release Date: 2007-12-16 |
> | Type notebook() for the GUI, and license() for information.|
> --
>
> sage: version()
> 'SAGE Version 2.9, Release Date: 2007-12-16'
>
> > that we are in reasonably good shape [William had feared that loads of
> > things would go *boom*].
>
> > Cheers,
>
> > Michael

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[David Joyner]

On Dec 16, 2007 11:19 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
> release on sage.math. While -long passed with flying colors, -optional
> had some failures in tut.tex since I didn't install some optional GAP
> database. But there are also some problems with maxima, which might

Maybe
database_gap-4.4.10
(There is also a newer version of this BTW.)

> just be fallout from the GAP failure. I will investigate, but it seems


I don't think we have (at this point) any functions which mix maxima
and GAP code.
(I wish there were and would be happy to be corrected!)

I did a sage -upgrade to 2.9 and had no serious problems but just notices that
the startup banner is missing "2.9". Is that just me?


[EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
--
| SAGE Version rc4, Release Date: 2007-12-16 |
| Type notebook() for the GUI, and license() for information.|
--

sage: version()
'SAGE Version 2.9, Release Date: 2007-12-16'


> that we are in reasonably good shape [William had feared that loads of
> things would go *boom*].
>
>
> Cheers,
>
> Michael
> >
>

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

Hello,

I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
release on sage.math. While -long passed with flying colors, -optional
had some failures in tut.tex since I didn't install some optional GAP
database. But there are also some problems with maxima, which might
just be fallout from the GAP failure. I will investigate, but it seems
that we are in reasonably good shape [William had feared that loads of
things would go *boom*].

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[mabshoff]

On Dec 17, 3:58 am, "Craig Citro" <[EMAIL PROTECTED]> wrote:
> > Sage 2.9 has been released. It is available at
>
> >http://sagemath.org/download.html
>
> So this built with no reported errors on my Mac Pro (Intel, 10.4.11).
> However, make check reported one error:
>
> sage -t  devel/sage-main/sage/stats/test.py
> **
> File "test.py", line 5:
> sage: import rpy
> Exception raised:
> Traceback (most recent call last):
>   File "/Users/craigcitro/sage-2.9/local/lib/python2.5/doctest.py",
> line 1212, in __run
> compileflags, 1) in test.globs
>   File "", line 1, in 
> import rpy###line 5:
> sage: import rpy
> ImportError: No module named rpy
> **
> 1 items had failures:
>1 of   1 in __main__.example_0
> ***Test Failed*** 1 failures.
>
> Looking at the install.log, it turns out that rpy failed to build, but
> this error wasn't propogated back to the r-2.6.1.p6 make process. So
> there are two issues:
>
> 1) Why did rpy fail?
> 2) Should this stop the build of R, or at least inform the user more 
> noticeably?
>
> For (1), the answer was easy: the rpy setup.py uses "tail -1" for
> "tail -n 1", which fails on some systems (namely mine). I'm running
> the most current version of textutils:
>
> [EMAIL PROTECTED] ~/sage-2.9/spkg/standard]  $ tail --version
> tail (textutils) 2.1
> Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, and Jim Meyering.
>
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> That's the most recent version according to the webpage, but the same
> version is installed on sage.math, where tail -1 works just fine.
> (This might have to do with the POSIX settings when tail was compiled?
> I vaguely got this impression from the FAQ on the textutils webpage.)
> So I'll report this upstream, but I suspect I should also add a patch
> to the rpy-1.0.1.spkg we ship, because I doubt I'm the only one with
> this issue. This is now trac ticket #1543, with a new rpy-1.0.1.spkg
> attached (since there's no mercurial repository in the spkg).
>
> 2) I would assume that we should halt the build if rpy fails for any
> reason; this is a simple 3-line fix in spkg-install, which I'm going
> to post on trac right now. (...) It's trac ticket #1542, with the
> simple patch attached.
>

Hi Craig,

as just mentioned in IRC I will review those patches/spkgs tonight [my
tonight since it is very early here at the moment] and I think rlm
should stick those in 2.9.1. We just need to bumb the version number
of rpy and as you observed fix the rpy.spkg name in the R.spkg itself,
too.

> -cc

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[David Joyner]

On Dec 16, 2007 11:04 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Sage 2.9 has been released. It is available at
>
>http://sagemath.org/download.html
>
> This is a *major* new release, with a huge number of tickets
> closed, and the additional of both R and the ATLAS BLAS
> as standard packages.
>
> If you're an *expert* user or just brave, do
>
>sage -upgrade


I had no serious problem with this on a 64 bit ubuntu machine.
However, it did open up a file emacs (yeah:-), as though it was doing a
hg_sage.commit(). I just got out of emacs without saving, aborting
something I guess, and it continued with the upgrade.


>
> but this may yield your sage temporarily unusable -- if that does happen,
> do email sage-support.
>
> If you're a beginner install from source or wait for new
> binaries to be posted in a few days (or less).
>
> ---
>
> The following people contributed this release:
>
>  * Michael Abshoff
>  * Martin Albrecht
>  * Robert Bradshaw
>  * Tom Boothby
>  * Ondrej Certik
>  * Craig Citro
>  * F. Clark
>  * John Cremona
>  * Alyson Deines
>  * Burcin Erocal
>  * Jan Groenewald
>  * David Harvey
>  * Mike Hansen
>  * Josh Kantor
>  * Robert Miller
>  * Bobby Moretti
>  * Rich Morin
>  * Bill Page
>  * Willem Jan Palenstijn
>  * Yi Qiang
>  * David Roe
>  * William Stein
>  * Carl Witty
>  * Paul Zimmermann
>
> Cheers,
>
> Michael Abshoff (release chair), William Stein
>
> * Major Features, New Spkgs and Bugfixes
>
> We achieved most of the goals we set ourselves for 2.9. The major
> changes compared to 2.8.15 are:
>
>  * Integration of PolyBoRi
>  * Integration of ATLAS BLAS/Lapack on non-OSX
>  * Integration of R 2.6.1 and rpy
>  * Update to FLINT 1.02
>  * Update to Symmetrica 2.0
>  * Much faster permutation arithmatic
>  * Very fast rubik's cube solvers
>  * Many build fixes applied and many bugs squashed
>
> We closed a total of 110 tickets, for details see below or our
> tracker at
>
> http://www.sagetrac.org/sage_trac/query?status=closed&milestone=sage-2.9
>
> * Known Issues with 2.9
>
> #1137: Import gd fails to import on OSX 10.4 ppc. Any attempt
>to fix this breaks other applications on different OSX
>flavors. We hope to fix this in 2.9.1.
> #1497: ATLAS fails to build on FC7, Dual core [known ATLAS
>issue with workaround: disable power management]
>
> * Upcoming Releases
>
> The following releases are planned for the rest of the year:
>
>  * 2.9.1: chaired by Robert Miller, bug fixes, release
>   planned about a week from now
>  * 2.9.2: chaired by Michael Abshoff, bug fixes, release
>   planned about two weeks from now
>
> 2.9.2 will be the release we plan to distribute on DVD at the AMS
> meeting, so we are shooting hard for an excellent release.
>
> * Doctesting Coverage
>
> For 2.9:
>
> Overall weighted coverage score:  35.3%
> Total number of functions:  17947
>
> Compared to 2.8.15 this is an increase by 0.5%.
>
> * About Sage (http://www.sagemath.org)
>
> Sage is developed by volunteers and combines 71 open source packages.
> It is available for download from sagemath.org and its mirrors in
> source or binary form. If you have any questions and/or problems
> please report them to the google groups sage-devel, sage-support,
> sage-forum or sage-newbie. You can also drop by in #sage-devel in
> freenode.
>
> * Closed Tickets:
>
> Merged in rc3:
>
> #1529: William Stein: update install_scripts to also install R script.
> #1530: William Stein: building tut.tex is currently broken
> #1531: Michael Abshoff: fix doctest failure sage/calculus/calculus.py
> #1532: Josh Kantor; Michael Abshoff: Error out with intelligent
>message if ATLAS tune failed
>
> Without tickets:
>
> William Stein: update libpng.spkg
> William Stein: don't let "sage -ba" start sage
> William Stein: link libcsage.so against atlas on non-OSX
> William Stein: link IML against atlas on non-OSX
> Willaim Stein, Michael Abshoff: Various doctest fixes
> Michael Abshoff: link LinBox against atlas on non-OSX
> Michael Abshoff: remove forced check from FLINT.spkg
>
> Merged in rc1/2:
>
> #1258: Willem Jan Palenstijn, Robert Miller: additions and changes
>to linear_codes
> #1457: William Stein: "BUG: Rational.__pow__ called on a non-Rational"
> #1464: Robert Miller: binary code canonical labels & automorphism
>group generators
> #1503: William Stein: formal function calls don't coerce correctly to
>Mathematica
> #1511: Robert Bradshaw: Export 3d objects in jmol format
> #1527: William Stein: doctest R with "import rpy"
> #1528: William Stein: make "sage -R" run R.
>
> Merged in rc0:
>
> #444: Robert Bradshaw: solve the rubik's cube fast!
> #553: Mike Hansen, William Stein: calling of symbolic expressions is
>   sometimes ridiculous
> #1077: Yi Qiang: DSage restarts two workers after timeout, various
>other fixes and improvements
> #1119: Martin Albrecht, Robert Bradshaw: EllipticCurve.random_eleme

[sage-support] Re: Sage-2.9

[Craig Citro]

> Sage 2.9 has been released. It is available at
>
>http://sagemath.org/download.html
>
>

So this built with no reported errors on my Mac Pro (Intel, 10.4.11).
However, make check reported one error:

sage -t  devel/sage-main/sage/stats/test.py
**
File "test.py", line 5:
sage: import rpy
Exception raised:
Traceback (most recent call last):
  File "/Users/craigcitro/sage-2.9/local/lib/python2.5/doctest.py",
line 1212, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
import rpy###line 5:
sage: import rpy
ImportError: No module named rpy
**
1 items had failures:
   1 of   1 in __main__.example_0
***Test Failed*** 1 failures.

Looking at the install.log, it turns out that rpy failed to build, but
this error wasn't propogated back to the r-2.6.1.p6 make process. So
there are two issues:

1) Why did rpy fail?
2) Should this stop the build of R, or at least inform the user more noticeably?

For (1), the answer was easy: the rpy setup.py uses "tail -1" for
"tail -n 1", which fails on some systems (namely mine). I'm running
the most current version of textutils:

[EMAIL PROTECTED] ~/sage-2.9/spkg/standard]  $ tail --version
tail (textutils) 2.1
Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, and Jim Meyering.

Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

That's the most recent version according to the webpage, but the same
version is installed on sage.math, where tail -1 works just fine.
(This might have to do with the POSIX settings when tail was compiled?
I vaguely got this impression from the FAQ on the textutils webpage.)
So I'll report this upstream, but I suspect I should also add a patch
to the rpy-1.0.1.spkg we ship, because I doubt I'm the only one with
this issue. This is now trac ticket #1543, with a new rpy-1.0.1.spkg
attached (since there's no mercurial repository in the spkg).

2) I would assume that we should halt the build if rpy fails for any
reason; this is a simple 3-line fix in spkg-install, which I'm going
to post on trac right now. (...) It's trac ticket #1542, with the
simple patch attached.

-cc

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---

[sage-support] Re: Sage-2.9

[Andrzej Giniewicz]

Just finished building it... it took over 7hours on my machine, but it
was worth it :)... btw - both 2 things about R are still actual in
2.9, that's "_" -> "." change for rpy to report version, and some
comments to enable optional package installation... apart from that it
is sweet :)... congratulations :)

btw... it's known that plotting in R doesn't work well yet, right?
using png() & dev.off() produces images with those numbers on it, and
using straight plot/hist from R, opens up X11 window with plot (those
numbers are also on it... I can make screenshot of it in X11 window if
it can help)

regards,
Andrzej.

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---