Okay, I got it to build. Haven't tested it yet, but...
I inserted these two different package updates into
sage-4.7.2/spkg/standard/
ecl-11.1.2.cvs2020.p0.spkg
readline-6.2.p2.spkg
of a freshly untarred sage-4.7.2. I then ran make
on it. This ran for 16.5 hours...
--
To
On Mon, Dec 05, 2011 at 10:42:13AM +, Dale Amon wrote:
Okay, I got it to build. Haven't tested it yet, but...
I inserted these two different package updates into
sage-4.7.2/spkg/standard/
ecl-11.1.2.cvs2020.p0.spkg
readline-6.2.p2.spkg
of a freshly untarred
On Sat, Dec 03, 2011 at 06:37:41PM -0800, Jonathan Bober wrote:
I'm not really sure. I'm hoping that someone else might have some more
advice. It would be easier to diagnose these failures if they could be
replicated.
Some other thoughts: More information about your machine might be useful,
In the process of setting up a fresh build I noticed
that I'd dropped that new ecl package into a directory
one level too high, so my last build did not really use
it I presume. I'll find out from this build if that affects
anything.
--
To post to this group, send an email to
WRT Memory - - It SEEMS that a Gig of RAM plus another Gig of Swap
is needed for Ubuntu 11.10 64 bit virtual machine.
I cannot say for sure that less will cause failures, only that this
config
runs close when building docs. Best not to be running much else
at the same time that is memory
On Sat, Dec 3, 2011 at 3:56 PM, Jonathan Bober jwbo...@gmail.com wrote:
Would it be enough to do
export SAGE_FAT_BINARY=yes
export SAGE_BINARY_BUILD=yes
export SAGE_ATLAS_ARCH=base
before building?
I don't know if this will work, but I decided I may as well give it a try.
The resulting
Yes, I had seen some reference to something like that. I think there is
also an option to set the cpuid. Unfortunately, these features do not seem
to be very well documented. For example, when I search google for
virtualbox synthcpu I get your mailing list post on the first page of
results, even
On Sun, Dec 04, 2011 at 03:26:23AM -0800, Jonathan Bober wrote:
On Sat, Dec 3, 2011 at 3:56 PM, Jonathan Bober jwbo...@gmail.com wrote:
Would it be enough to do
export SAGE_FAT_BINARY=yes
export SAGE_BINARY_BUILD=yes
export SAGE_ATLAS_ARCH=base
before building?
I don't know
Well, here is Dale's install.log:
http://sage.math.washington.edu/home/bober/dale-amon-20111203-install.log
I don't know what's going wrong.
On Sun, Dec 4, 2011 at 4:34 AM, Dale Amon a...@vnl.com wrote:
On Sun, Dec 04, 2011 at 03:26:23AM -0800, Jonathan Bober wrote:
On Sat, Dec 3, 2011 at
On Sun, Dec 04, 2011 at 03:38:41PM -0800, Jonathan Bober wrote:
Well, here is Dale's install.log:
http://sage.math.washington.edu/home/bober/dale-amon-20111203-install.log
I don't know what's going wrong.
It might be the ecl package. I've got it in the right place
now and my build has been
It's a shame this has gone unreplied to for so long. (Unless I missed a
reply in another thread. I'm may be confused by the various threads, which
is why I'm only replying on sage-devel.)
Are other people really having problems building on Ubuntu 11.10? I've had
no problems building sage 4.8.2 on
On Sat, Dec 3, 2011 at 3:56 PM, Jonathan Bober jwbo...@gmail.com wrote:
Are other people really having problems building on Ubuntu 11.10? I've had
no problems building sage 4.8.2 on 64-bit Ubuntu 11.10. Also, I just tried
on 32-bit 11.10 in a virtual machine, and sage built without any
On Sat, Dec 03, 2011 at 04:04:48PM -0800, Jonathan Bober wrote:
On Sat, Dec 3, 2011 at 3:56 PM, Jonathan Bober jwbo...@gmail.com wrote:
Are other people really having problems building on Ubuntu 11.10? I've had
no problems building sage 4.8.2 on 64-bit Ubuntu 11.10. Also, I just tried
on
I'm not really sure. I'm hoping that someone else might have some more
advice. It would be easier to diagnose these failures if they could be
replicated.
Some other thoughts: More information about your machine might be useful,
like the output from 'cat /proc/cpuinfo', and the amount of ram +
Despite being 32-bit, the VM still sees a very modern processor, though, so
it is possible something could go wrong on old hardware. If someone advises
me on exactly what to do, I could try building a binary that should be
usable on old machines. Would it be enough to do
export
On Tue, Nov 29, 2011 at 07:52:47PM -0800, Dima Pasechnik wrote:
Well, welcome to the bleeding edge development. :)
Oneiric is not currently supported by Sage, as you probably know.
No, it's not something to do with debian packages, it's most certainly
Sage's internal issue.
It could be an
The log says:
Filesystem error with pathname
#P/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-
5.23.2.p0/src/src/binary-ecl/maxima-package.fas.Either
1) the file does not exist, or 2) we are not allow to access the file,
or 3) the pathname points to a broken symbolic link..
So, what does
On Wednesday, 30 November 2011 19:10:54 UTC+8, DaleAmon wrote:
On Wed, Nov 30, 2011 at 03:06:50AM -0800, Dima Pasechnik wrote:
The log says:
Filesystem error with pathname
#P/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-
5.23.2.p0/src/src/binary-ecl/maxima-package.fas.Either
On Wed, Nov 30, 2011 at 03:19:32AM -0800, Dima Pasechnik wrote:
and what about
ls -l /root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-5.23.
2.p0/src/src/binary-ecl/*
?
Any files there at all?
ls -l
/root/TASK-SagemathBuild/sage-4.7.2/spkg/build/maxima-5.23.2.p0/src/src/binary-ecl/*
after all, it seems you need more things to be installed: the autotools
chain, i.e.
autoconf and automake.
I suppose it's autotools-dev package on oneiric.
Are they installed? If not, please install them, and re-run
./sage -f spkg/standard/maxima-5.23.2.p0.spkg
--
To post to this group, send
On Wed, Nov 30, 2011 at 04:33:28AM -0800, Dima Pasechnik wrote:
after all, it seems you need more things to be installed: the autotools
chain, i.e.
autoconf and automake.
I suppose it's autotools-dev package on oneiric.
They appear to already be installed:
*** Opt develautoconf
On Mon, Nov 28, 2011 at 07:54:23PM +, Dale Amon wrote:
On Mon, Nov 28, 2011 at 07:07:04AM -0800, Dima Pasechnik wrote:
Try installing
libreadline-dev
(this belongs to sage-support, so I cc there).
Dmitrii
Thanks. Seems this is something to add to the list of
required packages
Sorry, I was totally ignorant about the particular problem you had.
Basically, you will need to get an updated spkg for readline.
John already posted the link regading this on this thread:
On Tue, Nov 29, 2011 at 03:25:39AM -0800, Dima Pasechnik wrote:
Sorry, I was totally ignorant about the particular problem you had.
Basically, you will need to get an updated spkg for readline.
John already posted the link regading this on this thread:
Well, welcome to the bleeding edge development. :)
Oneiric is not currently supported by Sage, as you probably know.
No, it's not something to do with debian packages, it's most certainly
Sage's internal issue.
It could be an unusual combination of rather dated hardware and very new
OS release
Try installing
libreadline-dev
(this belongs to sage-support, so I cc there).
Dmitrii
--
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
On Mon, Nov 28, 2011 at 07:07:04AM -0800, Dima Pasechnik wrote:
Try installing
libreadline-dev
(this belongs to sage-support, so I cc there).
Dmitrii
Thanks. Seems this is something to add to the list of
required packages to be installed before starting.
I restarted make... so I will know
oops, I think I was too quick, sorry.
readline is now distributed with Sage.
So the error you got means that it was not properly installed, yet
the installation happily went further.
Could you look at install.log and find out whether readline, more precisely,
readline-6.1, installed OK?
Do
Try searching the group sage-devel (and possibly sage-release) for
readline configuring R. The following thread might be useful, for
example:
https://groups.google.com/forum/#!searchin/sage-devel/readline$20configuring$20r/sage-devel/B7y-ntx13Os/m2kJoygRxMYJ
--
John
--
To post to this
29 matches
Mail list logo
