> Perhaps. Please help us make Sage more mature in
> this regard.
I'm working on it with small pieces when I can ;-) (cf zlib prob
reports)
> I do not see Sage that way. I see Sage as being like a monolithic program
> such as Magma, vmware, Parallels, etc. It is very similar in size to those
Thanks. I've added this to http://trac.sagemath.org/sage_trac/ticket/2068
On Feb 5, 2008 2:43 PM, philt <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> libpng-1.2.22.p5 added this in spkg-install:
> LDFLAGS="-L\"$SAGE_LOCAL/lib\" $LDFLAGS"
>
> I tried the following modification:
> LDFLAGS="-L$SAGE_LOCAL
Hi,
libpng-1.2.22.p5 added this in spkg-install:
LDFLAGS="-L\"$SAGE_LOCAL/lib\" $LDFLAGS"
I tried the following modification:
LDFLAGS="-L$SAGE_LOCAL/lib $LDFLAGS"
and it worked.
The problem is that quoting the arg of -L seems still wise as the path
could contain a space but it seems it interfer
[EMAIL PROTECTED] sage-2.10.1-ia64-Linux]$ time ./sage -t devel/sage-main/
sage/graphs/graph_generators.py
sage -t devel/sage-main/sage/graphs/graph_generators.py
[144.7 s]
--
All tests passed!
Total time for all tests:
On Feb 5, 2008 1:18 PM, Kate <[EMAIL PROTECTED]> wrote:
>
> When I build sage-2.10.1 (using gcc-4.2.2) on my itanium-Linux
> box, 'make check' gives
>
> sage -t devel/sage-main/sage/graphs/graph_generators.py*** ***
> Error: TIMED OUT! *** ***
> *** *** Error: TIMED OUT! *** ***
>
> If I edit
When I build sage-2.10.1 (using gcc-4.2.2) on my itanium-Linux
box, 'make check' gives
sage -t devel/sage-main/sage/graphs/graph_generators.py*** ***
Error: TIMED OUT! *** ***
*** *** Error: TIMED OUT! *** ***
If I edit local/bin/sage-doctest and increase TIMEOUT to 240 (from
180), then whe
On Feb 5, 2008, at 11:12 AM, William Stein wrote:
> On Feb 5, 2008 10:31 AM, Robert Bradshaw
> <[EMAIL PROTECTED]> wrote:
>>
>> I'm not sure I like this idea...I think this creates a larger gap
>> between developers and users.
>
> True. I'm not a fan of such a gap, since I want every single us
On Feb 5, 2008 10:31 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>
> I'm not sure I like this idea...I think this creates a larger gap
> between developers and users.
True. I'm not a fan of such a gap, since I want every single user
to be a developer.
> It's a lot easier than downloading and
On Feb 5, 2008 9:58 AM, philt <[EMAIL PROTECTED]> wrote:
>
> > > Is the problem you are solving that with the current situation,
> > > you and sage-support) get too many silly build questions?
> > Yes.
>
> If it's easier to support a full install from sources from scratch
> than to support planned
> I did as you asked. I received a similar error when doing the upgrade
> after the gmp build. I posted the entire output of both commands
> here, in case that might be helpful:
>
> http://www.gordontillman.info/html/tmp/sage_upgrade_1.html
>
Hi Gordy,
I had the same problem doing sage -upgra
Burcin Erocal wrote:
> On Tue, 05 Feb 2008 09:06:57 -0600
> Jason Grout <[EMAIL PROTECTED]> wrote:
>
>> Burcin Erocal wrote:
>
>> Can we add the tuning information extraction to the spkg script or
>> somewhere that we can just type one command in (sage -tuning or
>> something) and get a tar fi
I'm not sure I like this idea...I think this creates a larger gap
between developers and users. It's a lot easier than downloading and
unpacking too.
I would propose that if the original install was a binary install,
and nothing has been changed, then the -upgrade command will download
th
> > Is the problem you are solving that with the current situation,
> > you and sage-support) get too many silly build questions?
> Yes.
If it's easier to support a full install from sources from scratch
than to support planned upgrades (we're not talking about release
candidates here), it only d
On Feb 5, 2008 9:10 AM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> Is the problem you are solving that with the current situation,
> you and sage-support) get too many silly build questions?
Yes.
> In any case, I vote to not make the command longer
> ("-upgrade" -> "-devel_upgrade" but shorter
Is the problem you are solving that with the current situation,
you and sage-support) get too many silly build questions?
In any case, I vote to not make the command longer
("-upgrade" -> "-devel_upgrade" but shorter ("-upgrade" -> "-u"),
because I am lazy:-).
On Feb 5, 2008 11:59 AM, William S
Hi,
I would like to propose again that we deprecate the
sage -upgrade
functionality for "normal end users". It was definitely never
meant to be used by anybody but developers -- in fact I wrote
it mainly for David Kohel (an early Sage developer) who lived
in Australia and consequentl
Thanks for the quick feedback Dr. Stein.
I did as you asked. I received a similar error when doing the upgrade
after the gmp build. I posted the entire output of both commands
here, in case that might be helpful:
http://www.gordontillman.info/html/tmp/sage_upgrade_1.html
--gordy
--~--~-
On Tue, 05 Feb 2008 09:06:57 -0600
Jason Grout <[EMAIL PROTECTED]> wrote:
> Burcin Erocal wrote:
> Can we add the tuning information extraction to the spkg script or
> somewhere that we can just type one command in (sage -tuning or
> something) and get a tar file we can upload? I can see this
Burcin Erocal wrote:
> On Sun, 3 Feb 2008 07:59:18 -0800 (PST)
> mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>> The key issue is that ATLAS's tolerance was exceeded and the build
>> failed. This is a known issue, i.e. #1641, and will be fixed in
>> 2.10.2. I didn't have time in the end to fix it, so
On Sun, 3 Feb 2008 07:59:18 -0800 (PST)
mabshoff <[EMAIL PROTECTED]> wrote:
> The key issue is that ATLAS's tolerance was exceeded and the build
> failed. This is a known issue, i.e. #1641, and will be fixed in
> 2.10.2. I didn't have time in the end to fix it, so sorry. Restarting
> the build o
On Feb 5, 2008 6:24 AM, gordyt <[EMAIL PROTECTED]> wrote:
>
> Greetings All!
>
> I tried to update my existing sage installation via sage -upgrade.
> Everything seemed to go smoothly until near the end when I received
> the error shown below.
Could you try forcing a rebuild of gmp, then restart t
Greetings All!
I tried to update my existing sage installation via sage -upgrade.
Everything seemed to go smoothly until near the end when I received
the error shown below. One thing caught my eye:
--
libtool: link: cannot find the library `/Users/was/build/sage-2.10/
local/lib/libgmp.l
I'm very sorry this got through. My fault, as I was half-asleep and clicking
buttons too quickly. He has been banned and the message removed from the
archives. - David Joyner
On Feb 5, 2008 6:51 AM, uzmar <[EMAIL PROTECTED]> wrote:
>
> Another Homosexual Fantasy
> by SkinDiver
>
>
> I posted a me
Another Homosexual Fantasy
by SkinDiver
I posted a message about fellating other men and I also think about
being sodomized bareback by many, many men - one after the other. My
p*nis gets so hard when I think about being the object of mens
pleasure. Do any other men ever feel this way? Does anyo
24 matches
Mail list logo
