On Monday, March 11, 2019 at 10:06:59 AM UTC, E. Madison Bray wrote:
>
> On Mon, Mar 11, 2019 at 10:43 AM Jeroen Demeyer > wrote:
> >
> > On 2019-03-11 10:42, E. Madison Bray wrote:
> > > The spkg-install script (e.g. under
> > > local/var/tmp/sage/build/patch-2.7.5/spkg-install) should star
On Mon, Mar 11, 2019 at 11:44 AM Dima Pasechnik wrote:
>
> On Mon, Mar 11, 2019 at 9:42 AM E. Madison Bray wrote:
> >
> > On Mon, Mar 11, 2019 at 8:51 AM Dima Pasechnik wrote:
> > >
> > > Switch to bash (chsh is the command to do it), or just install bash,
> > > and, before starting ./configure
On Mon, Mar 11, 2019 at 9:42 AM E. Madison Bray wrote:
>
> On Mon, Mar 11, 2019 at 8:51 AM Dima Pasechnik wrote:
> >
> > Switch to bash (chsh is the command to do it), or just install bash,
> > and, before starting ./configure and make,
> > start bash in terminal explicitly.
>
> The spkg-install
On Mon, Mar 11, 2019 at 10:43 AM Jeroen Demeyer wrote:
>
> On 2019-03-11 10:42, E. Madison Bray wrote:
> > The spkg-install script (e.g. under
> > local/var/tmp/sage/build/patch-2.7.5/spkg-install) should start with a
> > shebang line like
> >
> > #!/usr/bin/env bash
> >
> > So that should already
On 2019-03-11 10:42, E. Madison Bray wrote:
The spkg-install script (e.g. under
local/var/tmp/sage/build/patch-2.7.5/spkg-install) should start with a
shebang line like
#!/usr/bin/env bash
So that should already use the correct shell unless your `bash` is
actually something that is not bash-com
On Mon, Mar 11, 2019 at 8:51 AM Dima Pasechnik wrote:
>
> Switch to bash (chsh is the command to do it), or just install bash,
> and, before starting ./configure and make,
> start bash in terminal explicitly.
The spkg-install script (e.g. under
local/var/tmp/sage/build/patch-2.7.5/spkg-install) s
Switch to bash (chsh is the command to do it), or just install bash,
and, before starting ./configure and make,
start bash in terminal explicitly.
On Mon, Mar 11, 2019 at 3:11 AM Ai Bo wrote:
>
> I used source code, not binary. Yes, from the tarball.
> I tried with "gcc version 7.2.0 (GCC)" and g
OS info:
more /etc/os-release
NAME="SLES"
VERSION="11.4"
VERSION_ID="11.4"
PRETTY_NAME="SUSE Linux Enterprise Server 11 SP4"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:11:4"
On Sunday, March 10, 2019 at 8:11:39 PM UTC-7, Ai Bo wrote:
>
> I used source code, not binary. Yes, from the
I used source code, not binary. Yes, from the tarball.
I tried with "gcc version 7.2.0 (GCC)" and got same error message.
I am actually using csh, not bash.
OS info:
uname -m = x86_64
uname -r = 3.0.101-108.13.1.14249.0.PTF-default
uname -s = Linux
I did run configure before running make.
There a
It could also be that instead of using the source distribution to
build sage, you instead try to use a binary tarball.
You need to get the source tarball here:
http://www.sagemath.org/download-source.html (or use git and clone
from
https://github.com/sagemath/sage
On Sun, Mar 10, 2019 at 9:27 AM A
What shell are you using? I don't think it is much tested not for bash.
And is the exact version of your Linux? We only see Suse...
gcc 4.7.2 is definitely too old, but gcc 7.2 should be OK.
Please run ./configure before make, and see if it passes.
On Sun, Mar 10, 2019 at 9:27 AM Ai Bo wrote:
Error message:
** I masked the paths.
[patch-2.7.5] Target: x86_64-suse-linux
[patch-2.7.5] Configured with: ./configure --prefix=/xxxs/gcc/4.7.2
--libdir=/xxx/gcc/4.7.2/lib64 --libexecdir=/xxx/gcc/4.7.2/libexec
--bindir=/xxx/gcc/4.7.2/bin --with-ppl=/xxx/gcc/4.7.2
--enable-cloog-backend=ppl --
12 matches
Mail list logo
