texinfo is not necessary.
Just try
make build
On Sun, 12 Jun 2022, 15:48 David Kohel, wrote:
> This still gave the same error. If I instead deactivate conda, I get
> further, but
> with the homebrew installation it fails to find texinfo:
>
> configure:
>
> hint: installing the following
On Sun, Jun 12, 2022 at 1:23 PM David Kohel wrote:
>
> I'm been unable to compile Sage on my MacOS laptop (Monterrey, x86 intel)
>
> I've tried installing all homebrew packages requested, but it tends to
> still not
> find them (path problem?). I switched to using conda, following the
> direction
I'm been unable to compile Sage on my MacOS laptop (Monterrey, x86 intel)
I've tried installing all homebrew packages requested, but it tends to
still not
find them (path problem?). I switched to using conda, following the
directions
here:
https://doc.sagemath.org/html/en/installation/conda.
On Sun, Feb 24, 2019 at 8:22 PM Paul Clarke wrote:
>
> Ok, good to know. Where can I find that beta? I have cloned the github
> repository at git://github.com/sagemath/sage.git
> and it looks like the most recent version on the develop branch is 8.7.beta5
It's not necessary. Just install your L
A typo: beta6 -> beta5
You have the good version
Le 24/02/2019 à 20:22, Paul Clarke a écrit :
Ok, good to know. Where can I find that beta? I have cloned the github
repository at git://github.com/sagemath/sage.git
and it looks like the most recent version on the develop branch is 8.7.beta5
On
Ok, good to know. Where can I find that beta? I have cloned the github
repository at git://github.com/sagemath/sage.git
and it looks like the most recent version on the develop branch is 8.7.beta5
On Sunday, February 24, 2019 at 1:02:30 PM UTC-6, vdelecroix wrote:
>
> This was
>
> https://trac.
This was
https://trac.sagemath.org/ticket/27016
which is indeed merged in 8.7.beta6
Le 24/02/2019 à 20:00, Dima Pasechnik a écrit :
This looks like a known bug, fixed in the latest beta I believe.
On Sun, 24 Feb 2019 19:42 Paul Clarke, wrote:
Hello,
Sage failed during compilation of the gf
This looks like a known bug, fixed in the latest beta I believe.
On Sun, 24 Feb 2019 19:42 Paul Clarke, wrote:
> Hello,
> Sage failed during compilation of the gfortran component. It appears that
> the files were compiled successfully, but there was an error when copying
> them to their final de
Don't think so, because it is copying to and from locations on
/media/paul/str , which has 90 GB left on it. The root filesystem drive
only has 1 GB left, though.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group a
Check disks for space?
On Sun, Feb 24, 2019 at 12:42 Paul Clarke wrote:
> Hello,
> Sage failed during compilation of the gfortran component. It appears that
> the files were compiled successfully, but there was an error when copying
> them to their final destination.
>
> Here is the error messag
Hello,
Sage failed during compilation of the gfortran component. It appears that
the files were compiled successfully, but there was an error when copying
them to their final destination.
Here is the error message:
[gfortran-7.2.0] Copying package files from temporary location
/media/paul/str
Hi,
I used to compiled sage till version 7.0, but now it crashes and halt pc
at about the compilation of doc (but I think with the last 8.2 beta 3 it
was before because sage doesn't run). I have an AMD 8core and 16 Go RAM
ssd 250 Go) ubuntu 17.10 (and 18.04). I guess I haven't enaugh RAM now ?
On Fri, Nov 11, 2011 at 07:15:27AM +1300, Francois Bissey wrote:
> > On Wed, Nov 9, 2011 at 11:00 PM, Dan Drake wrote:
> > > On Wed, 09 Nov 2011 at 09:16PM -0500, Daniel Thau wrote:
> > > > Yeah, I considered that possibility. The md5sum for both the
> > >
> > > pre-compiled
> > >
> > > > versi
> On Wed, Nov 9, 2011 at 11:00 PM, Dan Drake wrote:
> > On Wed, 09 Nov 2011 at 09:16PM -0500, Daniel Thau wrote:
> > > Yeah, I considered that possibility. The md5sum for both the
> >
> > pre-compiled
> >
> > > version I tried and the source both matched what they were expected
> > > too.
> > >
On Wed, Nov 9, 2011 at 11:00 PM, Dan Drake wrote:
> On Wed, 09 Nov 2011 at 09:16PM -0500, Daniel Thau wrote:
> > Yeah, I considered that possibility. The md5sum for both the
> pre-compiled
> > version I tried and the source both matched what they were expected too.
> >
> > $ md5sum sage-4.7.2.ta
On Wed, 09 Nov 2011 at 09:16PM -0500, Daniel Thau wrote:
> Yeah, I considered that possibility. The md5sum for both the pre-compiled
> version I tried and the source both matched what they were expected too.
>
> $ md5sum sage-4.7.2.tar
> b3073997e6c7ec00a269f84ff2e54973 sage-4.7.2.tar
>
> Any o
On Wed, Nov 9, 2011 at 8:38 PM, Dan Drake wrote:
> On Wed, 09 Nov 2011 at 05:27PM -0500, Daniel Thau wrote:
>
> > That's alright; I'd rather build it from source to get whatever
> > benefits can result from that. However, I am having trouble with that
> > as well. Simply downloading the 4.7.2 s
On Wed, 09 Nov 2011 at 05:27PM -0500, Daniel Thau wrote:
> That's alright; I'd rather build it from source to get whatever
> benefits can result from that. However, I am having trouble with that
> as well. Simply downloading the 4.7.2 source, untaring, and running
> make results in errors. The
Hi,
I would like to be able to run Sage on a Centos 5.7 machine.
Simply downloading, untaring and running Sage 4.7.2 for RHEL 5.6
results in the following:
./sage
The Sage installation tree may have moved
(from /home/buildbot/build/sage/
rosemary-1/rosemary_binary/build/sage-4.7.2
to
/scratch/sa
19 matches
Mail list logo
