On May 3, 1:50 am, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> built fine of Arch linux 32 bit without any change, didn't run tests
> yet but will soon...
>
> anyway small off-topic - I was making spkg for R 2.7 and RPy 1.0.2 to
> see if it would work (2.7 have some nice Cairo graphic
Hi,
built fine of Arch linux 32 bit without any change, didn't run tests
yet but will soon...
anyway small off-topic - I was making spkg for R 2.7 and RPy 1.0.2 to
see if it would work (2.7 have some nice Cairo graphics driver in
addition to X11 and others, examples from wiki already works), but
John Cremona wrote:
Hi,
> Thanks for the explanations!
>
> For my own build, I recovered by doing "sage -ba" as previously
> reported. So I don't know whether the original problem (running sage
> for the first time after an apparently successful build) was caused by
> the SAGE_PBUILD thing or no
Thanks for the explanations!
For my own build, I recovered by doing "sage -ba" as previously
reported. So I don't know whether the original problem (running sage
for the first time after an apparently successful build) was caused by
the SAGE_PBUILD thing or not. Before doing "sage -ba" I also d
On May 1, 9:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> Thanks -- I mistakenly thought "pbuild" was short for "parallel build".
Yes, it is meant to emphasize the parallel nature. Gary builds
routinely with 8 cores on his box and it cuts down the build time in a
linear fashion.
On Thu, May 01, 2008 at 04:12:36AM -0600, Gary Furnish wrote:
>
> If you export SAGE_PBUILD=yes before you run make (so that it uses
> pbuild from the beginning) it is necessary to link site-packages
> yourself with the following command from $SAGE_ROOT:
> ln -s devel/sage/build/sage/ local/lib/p
On an ubuntu 7.10amd64 machine:
The following tests failed:
sage -t devel/sage/sage/server/simple/twist.py
Total time for all tests: 4833.6 seconds
Please see /home/wdj/wdj/sagefiles/sage-3.0.1.alpha1/tmp/test.log for
the complete log from this test.
[EMAIL PROTECTED]:~/wdj/sagefiles/s
Doing "sage -ba" sorted that out. Here is the result of --testall:
The following tests failed:
sage -t devel/sage/sage/server/simple/twist.py
sage -t devel/sage/sage/dsage/tests/testdoc.py
Both passed when rerun separately.
John
Linux host-57-71 2.6.18.8-0.3-default #1 SMP
Thanks -- I mistakenly thought "pbuild" was short for "parallel
build". If it is not about building Sage, while is it called
SAGE_PBUILD?
Anyway, can someone remind me what causes this and how to fix it?
SAGE build/upgrade complete!
[EMAIL PROTECTED]/sage
---
On May 1, 2008, at 11:08 AM, Jaap Spies wrote:
> mabshoff wrote:
>> Hello,
>>
>> this release should have been out two days ago, but somehow
>> general slowness and me spending a lot of time on various
>> porting issues did delay this release more than it should
>> have. Gary's pbuild should now
mabshoff wrote:
> Hello,
>
> this release should have been out two days ago, but somehow
> general slowness and me spending a lot of time on various
> porting issues did delay this release more than it should
> have. Gary's pbuild should now be fully functional, but it
> wasn't made the default b
The symlink is needed only after make completes when you try to run
sage, not to build it.
On Thu, May 1, 2008 at 11:18 AM, John Cremona <[EMAIL PROTECTED]> wrote:
>
> Gary, that does not work!
>
> [EMAIL PROTECTED] SAGE_PBUILD=yes
> [EMAIL PROTECTED] -s devel/sage/build/sage/
> local/lib/pyt
Gary, that does not work!
[EMAIL PROTECTED] SAGE_PBUILD=yes
[EMAIL PROTECTED] -s devel/sage/build/sage/ local/lib/python/site-packages/sage
ln: creating symbolic link `local/lib/python/site-packages/sage': No
such file or directory
This is in a freshly unpacked SAGE_ROOT, which does not yet have
mabshoff wrote:
> Hello,
>
> this release should have been out two days ago, but somehow
> general slowness and me spending a lot of time on various
> porting issues did delay this release more than it should
> have. Gary's pbuild should now be fully functional, but it
> wasn't made the default b
If you export SAGE_PBUILD=yes before you run make (so that it uses
pbuild from the beginning) it is necessary to link site-packages
yourself with the following command from $SAGE_ROOT:
ln -s devel/sage/build/sage/ local/lib/python/site-packages/sage
This will be fixed in rc0.
On Thu, May 1, 2008
15 matches
Mail list logo
