You also were saying that you have MAXIMA set to an installation of Maxima.
Note that Sage won't be able to use it. Sage uses Maxima in two ways:
as a Python module embedding ECL (with Maxima installed there)
and (something we work on to get rid of) interacting with Maxima built
with ECL with pexp
On Sun, Feb 5, 2023 at 12:44 PM 'Nasser M. Abbasi' via sage-release
wrote:
>
>
> I agree with you. I think the best thing for me, is just to make a brand new
> Virtual box, and install a new Linux and start everything from clean system.
> It will take me 2-3 days as I have to install few things
I agree with you. I think the best thing for me, is just to make a brand
new Virtual box, and install a new Linux and start everything from clean
system. It will take me 2-3 days as I have to install few things I need,
Then will try installing sagemath again after that.
Thanks for the help.
--
I suspect you have an installation of openblas, or/and some other
blas/lapack, in /usr/local - and this results in scipy being unable
to link it correctly.
(or perhaps it's not /usr/local, but some other location known to pkg-config)
numpy and scipy accumulated ~20 years of layer upon layer of o
Here is the output for the new command you posted
>ldd
local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
linux-vdso.so.1 (0x7ffd883d4000)
libcblas.so.3 => /usr/lib/libcblas.so.3 (0x7f25a6532000)
libopen
On Sun, Feb 5, 2023 at 9:58 AM Dima Pasechnik wrote:
>
> On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
> wrote:
> >
> >
> > Here is the output
> >
> > >ldd
> > >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cp
On Sun, Feb 5, 2023 at 9:04 AM 'Nasser M. Abbasi' via sage-release
wrote:
>
>
> Here is the output
>
> >ldd
> >/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
> linux-vdso.so.1 (0x7ffc53be9000)
Here is the output
>ldd
/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so
linux-vdso.so.1 (0x7ffc53be9000)
libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
libm.so.6 =>
one source of trouble might be your
LD_LIBRARY_PATH=/usr/local/lib:/mnt/g/public_html/scripts:
setting. Build systems are usually ignoring it, linking with "correct"
libraries,
but at runtime (e.g., while importing a Python module using libraries)
this might result in picking a wrong library
On Sat, Feb 4, 2023 at 1:51 PM 'Nasser M. Abbasi' via sage-release
wrote:
>
> "Was it an incremental build. If so,
>make distclean
> and
> build again from scratch."
>
> It was not an incremental build. I extracted the gzip file and did the steps
> I showed. So I do not need to do "make dist
On Sat, 4 Feb 2023, 13:51 'Nasser M. Abbasi' via sage-release, <
sage-release@googlegroups.com> wrote:
> "Was it an incremental build. If so,
>make distclean
> and
> build again from scratch."
>
> It was not an incremental build. I extracted the gzip file and did the
> steps I showed. So I do
"Was it an incremental build. If so,
make distclean
and
build again from scratch."
It was not an incremental build. I extracted the gzip file and did the
steps I showed. So I do not need to do "make distclean" since everything is
new.
But I repeated now everything again using "make distcle
Hello,
Was it an incremental build. If so,
make distclean
and
build again from scratch.
Anyhow, if you look in your istall.log you'll see problems with a number of
packages, e.g. fpylll, scipy.
[sagemath_doc_html-none] [manifolds] ImportError:
/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv
There are at least two different issues that breaks the build of the doc
for you:
[sagemath_doc_html-none] pkg_resources.DistributionNotFound: The
'fpylll<=0.5.9,>=0.5.9' distribution was not found and is required by
sagemath-standard
[sagemath_doc_html-none] Warning: Could not import
sage.ma
I get this error on Linux virtual box running
lsb_release -a
LSB Version:n/a
Distributor ID:ManjaroLinux
Description:Manjaro Linux
Release:22.0.0
Codename:Sikaris
After extracting the gzip file, these are the commands I did
unset SAGE_ROOT
unset SAGE_LOCAL
export GIAC=/u
On Fri, Feb 3, 2023 at 7:33 AM Sébastien Labbé wrote:
>
>
>
> On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gmail.com wrote:
> On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé wrote:
> ./bootstrap: 9: m4: Permission denied
> make: *** [Makefile:365 : configure] Erre
In Debian, there is no package `ranlib`, the `ranlib` *binary* is included
in the `binutils-`, which is depended upon by the pseudo-package
`binutils`.
HTH,
Le vendredi 3 février 2023 à 08:33:10 UTC+1, Sébastien Labbé a écrit :
> On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gma
On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gmail.com
wrote:
On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé wrote:
./bootstrap: 9: m4: Permission denied
make: *** [Makefile:365 : configure] Erreur 1
Do you have "." in PATH?
No
What does "which m4" say?
On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé wrote:
./bootstrap: 9: m4: Permission denied
make: *** [Makefile:365 : configure] Erreur 1
Do you have "." in PATH?
What does "which m4" say?
--
You received this message because you are subscribed to the Google Groups
"sage-r
On Thu, 2 Feb 2023, 17:30 Sébastien Labbé, wrote:
> On another machine running Ubuntu 22.04, installing sage from source from
> scratch, I get "m4: Permission denied" error during the "make configure".
> Should I "sudo make configure" ?
>
no. Something it either off with permissions in SAGE_ROOT
On Thursday, February 2, 2023 at 6:31:21 PM UTC+1 John H Palmieri wrote:
Some people have had an issue with Singular: the system version is too new.
Using "./configure --with-system-singular=no" (probably after "make
distclean"?) would help, if that's the problem. There is an upgrade ticket
for
Some people have had an issue with Singular: the system version is too new.
Using "./configure --with-system-singular=no" (probably after "make
distclean"?) would help, if that's the problem. There is an upgrade ticket
for Singular that has had many isses, but last time I checked, it had a
posi
On another machine running Ubuntu 22.04, installing sage from source from
scratch, I get "m4: Permission denied" error during the "make configure".
Should I "sudo make configure" ? Never done that before...
See below:
$ make configure
./bootstrap -d
make[1] : on entre dans le répertoire « /home
Thanks for the release.
On my side, I am stuck with the following. I was having the same issue with
the previous version. I saw I was not alone, but I still don't know what is
the solution? Anybody know? Make distclean?
Sébastien
[sagelib-9.8.rc0] installing. Log file:
/home/slabbe/GitBox/sa
Le lundi 30 janvier 2023 à 13:59:27 UTC+1, Eric Gourgoulhon a écrit :
On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
- incremental build (-j16) from 9.8.beta7, with system python (3.8.10): OK
- make ptestlong --> all tests passed except for
sage -t --long --warn-long 66.8
--random-seed=818
BTW : please consider including #34935 (already positively reviewed...).
Le lundi 30 janvier 2023 à 18:24:38 UTC+1, Emmanuel Charpentier a écrit :
> On Debian testing running on core i7 + 16 GB RAM :
>
> - upgrading 9.8.beta7 + #34935 fails ; I had to go the `make distclean ;
> ... ` way.
>
> -
On Debian testing running on core i7 + 16 GB RAM :
- upgrading 9.8.beta7 + #34935 fails ; I had to go the `make distclean ;
... ` way.
- `ptestlong` gives the same three permanent failures already reported for
a while
- reinstalling `mathics` and `pari_jupyter`fail.
HTH,
Le lundi 30 janvier
On Ubuntu 20.04 running on Xeon E5-2623 + 16 GB RAM:
- incremental build (-j16) from 9.8.beta7, with system python (3.8.10): OK
- make ptestlong --> all tests passed except for
sage -t --long --warn-long 66.8
--random-seed=81878619703120460056743231466438357448 src/sage/env.py
**
Please consider #34873 for this release.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on th
29 matches
Mail list logo
