Hi,
I'm receiving a similar error message. What exactly did you do to fix the
problem?
Thanks
On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
>
> Indeed, sage did not start... After fixing it, sagenb installs.
>
> The error message is really confusing.
>
> Le 21/04/2019 à
On Tuesday, May 28, 2019 at 1:40:45 PM UTC+2, Michael Orlitzky wrote:
>
> On 5/25/19 12:49 PM, Sébastien Labbé wrote:
> >
> > (sage-sh) $ cd /tmp
> > (sage-sh) $ pwd
> > /tmp
> > (sage-sh) $ sh configure
> > sh: 0: Can't open configure
> >
>
> This means that the "configure" file isn't
On Tue, May 28, 2019 at 6:43 PM Christian Stump
wrote:
>
> > well, building gcc 7 with a 7-years old complier (gcc version 4.4.7
> > 20120313 (Red Hat 4.4.7-23), as the log says)
> > probably not possible.
> > Do they have something newer installed?
>
> They did install for me both gcc-7.2.0
> well, building gcc 7 with a 7-years old complier (gcc version 4.4.7
> 20120313 (Red Hat 4.4.7-23), as the log says)
> probably not possible.
> Do they have something newer installed?
They did install for me both gcc-7.2.0 (didn't work) and gcc-7.3.0 (didn't
work either).
Let me emphasize
well, building gcc 7 with a 7-years old complier (gcc version 4.4.7
20120313 (Red Hat 4.4.7-23), as the log says)
probably not possible.
Do they have something newer installed?
On Tue, May 28, 2019 at 4:17 PM Christian Stump
wrote:
>
> > ./configure --with-mp=mpir
> > make
>
> This did not work
> ./configure --with-mp=mpir
> make
This did not work -- but if I do not provide any gcc, sage compiles its own
and this works for gcc-7.2.0 on sage-8.6 while it does not work for the
same gcc-7.2.0 on sage-8.7. You find the log for the failing gcc-7.2.0
attached.
--
You received this
To expand on Dima's answer, when resuming work on an old branch with
intention of eventually merging it into the current development version (or
at least a more recent develop in the near future), I would suggest
habitually, if not *always* rebasing in the current version of develop. To
summarize
On Tue, May 28, 2019 at 1:50 PM Christian Stump
wrote:
>
> Thanks Dima! -- here is the requested information:
>
> It's a fresh install, config.log is attached. In just this moment, the system
> admin told me that he was able to compile sage-8.6 using the standard gcc
> compiler by RHEL6 (this
patchbots are more or less OK, see my answer on the ticket.
You ought to rebase this branch over the latest beta, before trying to build it.
(it's based on a very old version of Sage that doesn't work on OSX
10.14, I think)
Hope this helps.
On Tue, May 28, 2019 at 2:20 PM Anna Haensch wrote:
>
Hi All,
I'm returning to an old ticket that's been on trac for awhile
(#19112...most recent milestone Sage-7.1). The patchbot has failed, so I
know that something isn't right. I just tried to download and "make"
the branch and it raised an error, see below:
[gcc-4.9.3.p1] #define _VSTD
Thanks Dima! -- here is the requested information:
It's a fresh install, config.log is attached. In just this moment, the
system admin told me that he was able to compile sage-8.6 using the
standard gcc compiler by RHEL6 (this is copy-and-paste, I don't know what
that means), while the error
On 5/25/19 12:49 PM, Sébastien Labbé wrote:
>
> (sage-sh) $ cd /tmp
> (sage-sh) $ pwd
> /tmp
> (sage-sh) $ sh configure
> sh: 0: Can't open configure
>
This means that the "configure" file isn't coming from your PATH, which
is even more weird (where the hell is it coming from?).
First, can you
I suspect you don't have libgmpxx installed. What is the output of
$ find /usr/ -name libgmpxx.so*
and of
$ find /usr/ -name libgmp.so*
On Tue, May 28, 2019 at 9:54 AM Dima Pasechnik wrote:
>
> could you attach Sage's config.log ?
> I suspect that the system installation of GMP is a bit
could you attach Sage's config.log ?
I suspect that the system installation of GMP is a bit broken or
incomplete, or perhaps there are more than one, and they clash. (and our
recent GMP checking code fails to pick it up)
is it a fresh install, or an update?
--
anyhow, you can force the use
14 matches
Mail list logo