On Feb 4, 5:45 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On Feb 4, 12:35 am, Francois <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
>
>
> Hi Nils,
>
>
>
> > > I suspect that attaching a 13MB install.log is not the right method of
> > > supplying that info.
>
> > I had that kind of stuff be
On Feb 3, 2008, at 21:13 , mabshoff wrote:
> On Feb 4, 6:05 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
>> On Feb 2, 2008, at 20:10 , mabshoff wrote:
>>> Hello folks,
>>
>>> Sage 2.10.1 has been released on February 2nd, 2008. It is available
>>> at
>>
>>>http://sagemath.org/dow
On Feb 4, 6:05 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Feb 2, 2008, at 20:10 , mabshoff wrote:
>
>
>
> > Hello folks,
>
> > Sage 2.10.1 has been released on February 2nd, 2008. It is available
> > at
>
> >http://sagemath.org/download.html
>
> Full builds:
>
> Mac OS X,
On Feb 2, 2008, at 20:10 , mabshoff wrote:
>
> Hello folks,
>
> Sage 2.10.1 has been released on February 2nd, 2008. It is available
> at
>
>http://sagemath.org/download.html
Full builds:
Mac OS X, 10.4.11 (Dual Quad Xeon, "-j6"):
real74m34.964s
user57m14.
On Feb 4, 12:20 am, philt <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I had many troubles getting the upgrade through a caching proxy on
> which I've no control.
> When running sage -upgrade, the proxy didn't let me getting the latest
> versions, which made troubles with the critical
> files:http:/
On Feb 4, 12:35 am, Francois <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Nils,
>
> > I suspect that attaching a 13MB install.log is not the right method of
> > supplying that info.
>
> I had that kind of stuff before, can you look at the end of the
> install.log
> to see if it says:
> sage: An error
On Feb 4, 2:55 am, Francois <[EMAIL PROTECTED]> wrote:
> On Feb 4, 12:25 pm, Francois <[EMAIL PROTECTED]> wrote:
Hi Francois,
> > It doesn't use the new mechanism for using system atlas.
> > After thinking long and hard about it, I initially decided to
> > use it only to back off once I unders
On Feb 4, 12:21 am, "Craig Citro" <[EMAIL PROTECTED]> wrote:
> Hi all,
Hi,
> So I just tried to do a sage -upgrade, and it failed trying to install
> mpfi. The log showed that libgmp.la was complaining that it was
> relocated; indeed, libgmp.la contained the following lines at the end:
>
> # D
On Feb 3, 11:55 pm, philt <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I first installed and compiled the sources 2.10 without any problems
> last week.
>
> Now I ran sage -upgrade and I got an error about missing zlib headers
> when compiling libpng: "checking for zlibVersion in -lz..."
> I then ins
On Feb 4, 12:25 pm, Francois <[EMAIL PROTECTED]> wrote:
> It doesn't use the new mechanism for using system atlas.
> After thinking long and hard about it, I initially decided to
> use it only to back off once I understood the mechanism.
> So here is what I think is wrong with it:
> It check fo
Hi,
On Feb 4, 12:25 pm, Nils Bruin <[EMAIL PROTECTED]> wrote:
> I tried a "sage --upgrade" from a clean, relocated install of sage
> 2.10. The install seems to succeed, but running sage leads to:
>
> --
> | SAGE Version 2.10.1, R
Hello,
I know it was already discussed and I'm quoting
http://trac.sagemath.org/sage_trac/ticket/1556
:
> So maybe you are talking about semi-private servers that have a fixed list
> of accounts and users, like a normal UNIX system say, where potential
> users cannot sign up for a new account -
Hello,
I first installed and compiled the sources 2.10 without any problems
last week.
Now I ran sage -upgrade and I got an error about missing zlib headers
when compiling libpng: "checking for zlibVersion in -lz..."
I then installed the host package (debian: zlib1g-dev) and ran again
sage -upgr
Hello,
I had many troubles getting the upgrade through a caching proxy on
which I've no control.
When running sage -upgrade, the proxy didn't let me getting the latest
versions, which made troubles with the critical files:
http://www.sagemath.org/packages/standard/list
http://www.sagemath.org/pac
Hi all,
I updated the ebuild in
http://bugs.gentoo.org/show_bug.cgi?id=201321
for sage-2.10.1.
A few things to mention:
-Cleaned and tidying up a little bit.
-bumped dependencies to put them in line with sage.
-Added a further notice to the maxima warning.
-Added a notice on licenses as sage itse
I tried a "sage --upgrade" from a clean, relocated install of sage
2.10. The install seems to succeed, but running sage leads to:
--
| SAGE Version 2.10.1, Release Date: 2008-02-02 |
| Type notebook() for the
Hi all,
So I just tried to do a sage -upgrade, and it failed trying to install
mpfi. The log showed that libgmp.la was complaining that it was
relocated; indeed, libgmp.la contained the following lines at the end:
# Directory that this library needs to be installed in:
libdir='/Users/craigcitro/
On Feb 3, 10:08 am, vgermrk <[EMAIL PROTECTED]> wrote:
> The build fails on my notebook (Intel(R) Pentium(R) M processor
> 1400MHz), Ubuntu 7.10 (2.6.22-14-generic).
> I compiled older versions of sage a few times before on this machine,
> but this time i get errors.
> Thanks in advance for any
The build fails on my notebook (Intel(R) Pentium(R) M processor
1400MHz), Ubuntu 7.10 (2.6.22-14-generic).
I compiled older versions of sage a few times before on this machine,
but this time i get errors.
Thanks in advance for any help.
The full install.log is at
http://homepage.rub.de/michael.
19 matches
Mail list logo
