On 05/23/10 02:30 PM, geep999 wrote:
Mea culpa.
I hadn't got into the Sage way of doing things and didn't realize that
the build would be alongside the Sage source tree created from
sage-4.4.2.tar. Maybe README.txt should mention this. Or it's
somewhere and I haven't noticed it.
I don't feel README.txt needs to mention that, as this is how 99% of programs
are built. Conversely, if Sage did always build under $HOME, then it would be
right to mention it, as it would be almost unique in doing that.
For some reason I thought it was going to build under $HOME - where I
have little space.
That would be very unusual for a program to do that.
The only other strategy I know of is a few programs will refuse to build inside
the directory where the sources are. It is certainly recommended one does not
build gcc in the same directory as the gcc source. But 99% of programs are built
in this directory. After building, typing 'make distclean' will remove all the
built files for many programs, though not all.
So I used DESTDIR to make it build where I have lots of free space.
Using DESTDIR seems to have caused all the problems.
I don't believe DESTDIR is anything used by Sage. Even thought things that are
used by Sage (CC, CXX, CFLAGS, MAKE) are not used consistently. But I'm not even
aware of DESTFIR being documented.
Anyway, all 2.1 Gb of Sage is now built, documentation created and
notebook seems OK with Firefox.
Great.
Now to learn how to use it...
That is the more difficult bit!
Thanks for your help everybody.
Cheers, Peter
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
