[sage-release] Re: Sage 9.8.rc1 released

[Matthias Köppe]

I've fast-forwarded develop to 9.8.rc1 on https://github.com/sagemath/sage

On Sunday, February 5, 2023 at 9:21:45 AM UTC-8 Volker Braun wrote:

> tag is pushed!
>
> On Sunday, February 5, 2023 at 5:58:59 PM UTC+1 matthia...@gmail.com 
> wrote:
>
>> Thanks for the new rc. It's currently not tagged on vbraun/sage though; 
>> could you push the tag please?
>>
>> On Sunday, February 5, 2023 at 6:14:57 AM UTC-8 Volker Braun wrote:
>>
>>> Note: the old trac git server is already disabled and the new 
>>> https://github.com/sagemath/sage is still locked for migration, so you 
>>> will only be able to get the branch from there starting tomorrow (Monday). 
>>> If you are dying to see the new version you can temporarily get it from my 
>>> own fork at github.com:vbraun/sage, but I'd recommend waiting until 
>>> tomorrow.
>>>
>>> As always, you can get the latest beta version from the "develop" git 
>>> branch. Alternatively, the self-contained source tarball is at 
>>> http://www.sagemath.org/download-latest.html
>>>
>>>
>>> 200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to 
>>> 9.8.rc1
>>> 2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for 
>>> portability workflows
>>> 1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
>>> 77173ef550c Trac #34873: Deprecate 
>>> sage.homology.graded_resolution.GradedFreeResolution
>>> 9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to 
>>> 9.8.rc0
>>>
>>

-- 
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 the web visit 
https://groups.google.com/d/msgid/sage-release/672f2d9a-7f14-404f-bf89-ccb35e631bf3n%40googlegroups.com.

Re: [sage-release] Sage 9.8.rc1 released

[Thierry Dumont]

On Debian testing (debian 12), migration from rcà to rc1 without any 
problem.


Le 05/02/2023 à 15:14, Volker Braun a écrit :
Note: the old trac git server is already disabled and the new 
https://github.com/sagemath/sage is still locked for migration, so you 
will only be able to get the branch from there starting tomorrow 
(Monday). If you are dying to see the new version you can temporarily 
get it from my own fork at github.com:vbraun/sage, but I'd recommend 
waiting until tomorrow.


As always, you can get the latest beta version from the "develop" git 
branch. Alternatively, the self-contained source tarball is at 
http://www.sagemath.org/download-latest.html



200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to 
9.8.rc1
2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for 
portability workflows

1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
77173ef550c Trac #34873: Deprecate 
sage.homology.graded_resolution.GradedFreeResolution

9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to 9.8.rc0

--
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 the web visit 
https://groups.google.com/d/msgid/sage-release/98556973-2a19-4fe2-8bbe-6e6804612671n%40googlegroups.com .


--
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 the web visit 
https://groups.google.com/d/msgid/sage-release/fe64aa44-802a-1ddd-e528-1f6c2225b76b%40math.univ-lyon1.fr.

[sage-release] Re: Sage 9.8.rc1 released

[Volker Braun]

tag is pushed!

On Sunday, February 5, 2023 at 5:58:59 PM UTC+1 matthia...@gmail.com wrote:

> Thanks for the new rc. It's currently not tagged on vbraun/sage though; 
> could you push the tag please?
>
> On Sunday, February 5, 2023 at 6:14:57 AM UTC-8 Volker Braun wrote:
>
>> Note: the old trac git server is already disabled and the new 
>> https://github.com/sagemath/sage is still locked for migration, so you 
>> will only be able to get the branch from there starting tomorrow (Monday). 
>> If you are dying to see the new version you can temporarily get it from my 
>> own fork at github.com:vbraun/sage, but I'd recommend waiting until 
>> tomorrow.
>>
>> As always, you can get the latest beta version from the "develop" git 
>> branch. Alternatively, the self-contained source tarball is at 
>> http://www.sagemath.org/download-latest.html
>>
>>
>> 200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to 
>> 9.8.rc1
>> 2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for 
>> portability workflows
>> 1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
>> 77173ef550c Trac #34873: Deprecate 
>> sage.homology.graded_resolution.GradedFreeResolution
>> 9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to 
>> 9.8.rc0
>>
>

-- 
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 the web visit 
https://groups.google.com/d/msgid/sage-release/6e6d5396-19e4-4f2e-8fe0-38e31610ee72n%40googlegroups.com.

[sage-release] Re: Sage 9.8.rc1 released

[Matthias Köppe]

Thanks for the new rc. It's currently not tagged on vbraun/sage though; 
could you push the tag please?

On Sunday, February 5, 2023 at 6:14:57 AM UTC-8 Volker Braun wrote:

> Note: the old trac git server is already disabled and the new 
> https://github.com/sagemath/sage is still locked for migration, so you 
> will only be able to get the branch from there starting tomorrow (Monday). 
> If you are dying to see the new version you can temporarily get it from my 
> own fork at github.com:vbraun/sage, but I'd recommend waiting until 
> tomorrow.
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> 200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to 
> 9.8.rc1
> 2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for 
> portability workflows
> 1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
> 77173ef550c Trac #34873: Deprecate 
> sage.homology.graded_resolution.GradedFreeResolution
> 9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to 
> 9.8.rc0
>

-- 
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 the web visit 
https://groups.google.com/d/msgid/sage-release/036ef978-d330-453b-b9f0-b4b6a63d408dn%40googlegroups.com.

[sage-release] Sage 9.8.rc1 released

[Volker Braun]

Note: the old trac git server is already disabled and the new 
https://github.com/sagemath/sage is still locked for migration, so you will 
only be able to get the branch from there starting tomorrow (Monday). If 
you are dying to see the new version you can temporarily get it from my own 
fork at github.com:vbraun/sage, but I'd recommend waiting until tomorrow.

As always, you can get the latest beta version from the "develop" git 
branch. Alternatively, the self-contained source tarball is at 
http://www.sagemath.org/download-latest.html


200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to 
9.8.rc1
2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for 
portability workflows
1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
77173ef550c Trac #34873: Deprecate 
sage.homology.graded_resolution.GradedFreeResolution
9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to 9.8.rc0

-- 
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 the web visit 
https://groups.google.com/d/msgid/sage-release/98556973-2a19-4fe2-8bbe-6e6804612671n%40googlegroups.com.

Re: [sage-release] Re: Sage 9.8.rc0 released

[Dima Pasechnik]

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 pexpect (Unix pipes, more or less).
While the latter may in principle use different Maxima installation,
this is not implemented.




On Sun, Feb 5, 2023 at 12:56 PM Dima Pasechnik  wrote:
>
> 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 need, 
> > Then will try installing sagemath again after that.
>
> you can try to temporarily move /usr/local somewhere, and see if it
> helps; no need to rebuild the whole Sage then, just rebuild
> scipy:
>
> make scipy-clean scipy-uninstall
> make scipy
>
> Then start sage
>
>  ./sage
>
> and run
>
>  sage:  import scipy
>
> there. If this works, run
>
> make
>
> to see if it finishes fine.
>
> >
> > Thanks for the help.
> > --Nasser
> >
> > On Sunday, February 5, 2023 at 5:58:14 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> 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 old
> >> outdated code for recognising BLAS/LAPACK libraries, it's such a
> >> nightmare to debug.
> >>
> >>
> >>
> >> On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
> >>  wrote:
> >> >
> >> > 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)
> >> > libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
> >> > libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
> >> > libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
> >> > /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
> >> > libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
> >> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
> >> > >
> >> >
> >> > I've also put in same folder here a file called log_folders.tar.gz which 
> >> > is backup of the logs/ folder in my build tree of 9.8 rc0 so it will 
> >> > have the logs you asked for.
> >> >
> >> > any other information needed please let me know.
> >> > --Nasser
> >> >
> >> >
> >> > On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
> >> >>
> >> >> 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.cpython-310-x86_64-linux-gnu.so
> >> >> > > linux-vdso.so.1 (0x7ffc53be9000)
> >> >> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> >> >> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> >> >> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> >> >> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> >> >> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> >> >> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
> >> >> > > (0x7fc232444000)
> >> >> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
> >> >> >
> >> >> > here is how it looks on a non-broken installation.
> >> >> >
> >> >> > $ ldd 
> >> >> > 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 (0x7ffe6b935000)
> >> >> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
> >> >> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
> >> >> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
> >> >> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
> >> >> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
> >> >> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
> >> >> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
> >> >> > /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
> >> >> >
> >> >> > As you see, in your case libopenblas.so is not there, and you have an
> >> >> > error due to this.
> >> >> > Why scipy builds such a broken module, I don't know. I'd say it's a 
> >> >> > scipy bug.

Re: [sage-release] Re: Sage 9.8.rc0 released

[Dima Pasechnik]

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 need, Then will 
> try installing sagemath again after that.

you can try to temporarily move /usr/local somewhere, and see if it
helps; no need to rebuild the whole Sage then, just rebuild
scipy:

make scipy-clean scipy-uninstall
make scipy

Then start sage

 ./sage

and run

 sage:  import scipy

there. If this works, run

make

to see if it finishes fine.

>
> Thanks for the help.
> --Nasser
>
> On Sunday, February 5, 2023 at 5:58:14 AM UTC-6 Dima Pasechnik wrote:
>>
>> 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 old
>> outdated code for recognising BLAS/LAPACK libraries, it's such a
>> nightmare to debug.
>>
>>
>>
>> On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
>>  wrote:
>> >
>> > 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)
>> > libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
>> > libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
>> > libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
>> > /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
>> > libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
>> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
>> > >
>> >
>> > I've also put in same folder here a file called log_folders.tar.gz which 
>> > is backup of the logs/ folder in my build tree of 9.8 rc0 so it will have 
>> > the logs you asked for.
>> >
>> > any other information needed please let me know.
>> > --Nasser
>> >
>> >
>> > On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
>> >>
>> >> 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.cpython-310-x86_64-linux-gnu.so
>> >> > > linux-vdso.so.1 (0x7ffc53be9000)
>> >> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
>> >> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
>> >> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
>> >> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
>> >> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
>> >> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
>> >> > > (0x7fc232444000)
>> >> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>> >> >
>> >> > here is how it looks on a non-broken installation.
>> >> >
>> >> > $ ldd 
>> >> > 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 (0x7ffe6b935000)
>> >> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
>> >> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
>> >> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
>> >> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
>> >> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
>> >> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
>> >> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
>> >> > /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
>> >> >
>> >> > As you see, in your case libopenblas.so is not there, and you have an
>> >> > error due to this.
>> >> > Why scipy builds such a broken module, I don't know. I'd say it's a 
>> >> > scipy bug.
>> >> >
>> >> > Please post logs/pkgs/numpy* and logs/pkgs/scipy*
>> >>
>> >> please also check that
>> >>
>> >> ldd 
>> >> local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
>> >>
>> >> has openblas in its output.
>> >>
>> >> >
>> >> >
>> >> > > >
>> >> > >
>> >> > > "You should add fpylll at the end of the line in
>> >> > >
>> >> > > build/pkgs/sagemath_doc_html/dependencies
>> >> > >
>> >> > > and run ./configure and make again"
>> >> > >
>> >> > > Ok thanks. Will give this a try.
>> >> > >
>> >> > > "sage in a different directory which is in your PATH typically breaks 
>> >> > > things"
>> >> > >
>> >> > > but it is NOT in 

Re: [sage-release] Re: Sage 9.8.rc0 released

['Nasser M. Abbasi' via sage-release]

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.
--Nasser

On Sunday, February 5, 2023 at 5:58:14 AM UTC-6 Dima Pasechnik wrote:

> 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 old
> outdated code for recognising BLAS/LAPACK libraries, it's such a
> nightmare to debug.
>
>
>
> On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
>  wrote:
> >
> > 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)
> > libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
> > libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
> > libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
> > /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
> > libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
> > >
> >
> > I've also put in same folder here a file called log_folders.tar.gz which 
> is backup of the logs/ folder in my build tree of 9.8 rc0 so it will have 
> the logs you asked for.
> >
> > any other information needed please let me know.
> > --Nasser
> >
> >
> > On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> 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.cpython-310-x86_64-linux-gnu.so
> >> > > linux-vdso.so.1 (0x7ffc53be9000)
> >> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> >> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> >> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> >> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> >> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> >> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
> (0x7fc232444000)
> >> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
> >> >
> >> > here is how it looks on a non-broken installation.
> >> >
> >> > $ ldd 
> 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 (0x7ffe6b935000)
> >> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
> >> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
> >> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
> >> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
> >> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
> >> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
> >> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
> >> > /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
> >> >
> >> > As you see, in your case libopenblas.so is not there, and you have an
> >> > error due to this.
> >> > Why scipy builds such a broken module, I don't know. I'd say it's a 
> scipy bug.
> >> >
> >> > Please post logs/pkgs/numpy* and logs/pkgs/scipy*
> >>
> >> please also check that
> >>
> >> ldd 
> local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_
> multiarray_umath.cpython-310-x86_64-linux-gnu.so
> >>
> >> has openblas in its output.
> >>
> >> >
> >> >
> >> > > >
> >> > >
> >> > > "You should add fpylll at the end of the line in
> >> > >
> >> > > build/pkgs/sagemath_doc_html/dependencies
> >> > >
> >> > > and run ./configure and make again"
> >> > >
> >> > > Ok thanks. Will give this a try.
> >> > >
> >> > > "sage in a different directory which is in your PATH typically 
> breaks things"
> >> > >
> >> > > but it is NOT in the path. This is the reason I do
> >> > >
> >> > > unset SAGE_ROOT
> >> > > unset SAGE_LOCAL
> >> > >
> >> > > before building any new release. I make sure current installed 
> sagemath (in different folder) is not visible.
> >> > >
> >> > > --Nasser
> >> > >
> >> > > On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik 
> wrote:
> >> > >>
> >> > >> 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
> >> > >> > 

Re: [sage-release] Re: Sage 9.8.rc0 released

[Dima Pasechnik]

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 old
outdated code for recognising BLAS/LAPACK libraries, it's such a
nightmare to debug.



On Sun, Feb 5, 2023 at 10:36 AM 'Nasser M. Abbasi' via sage-release
 wrote:
>
> 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)
> libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
> libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
> libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
> /usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
> libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
> libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
> >
>
> I've also put in same folder here  a file called log_folders.tar.gz  which is 
> backup of the logs/ folder in my build tree of 9.8 rc0 so it will have the 
> logs you asked for.
>
> any other information needed please let me know.
> --Nasser
>
>
> On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:
>>
>> 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.cpython-310-x86_64-linux-gnu.so
>> > > linux-vdso.so.1 (0x7ffc53be9000)
>> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
>> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
>> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
>> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
>> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
>> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 (0x7fc232444000)
>> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>> >
>> > here is how it looks on a non-broken installation.
>> >
>> > $ ldd 
>> > 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 (0x7ffe6b935000)
>> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
>> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
>> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
>> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
>> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
>> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
>> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
>> > /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
>> >
>> > As you see, in your case libopenblas.so is not there, and you have an
>> > error due to this.
>> > Why scipy builds such a broken module, I don't know. I'd say it's a scipy 
>> > bug.
>> >
>> > Please post logs/pkgs/numpy* and logs/pkgs/scipy*
>>
>> please also check that
>>
>> ldd 
>> local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so
>>
>> has openblas in its output.
>>
>> >
>> >
>> > > >
>> > >
>> > > "You should add fpylll at the end of the line in
>> > >
>> > > build/pkgs/sagemath_doc_html/dependencies
>> > >
>> > > and run ./configure and make again"
>> > >
>> > > Ok thanks. Will give this a try.
>> > >
>> > > "sage in a different directory which is in your PATH typically breaks 
>> > > things"
>> > >
>> > > but it is NOT in the path. This is the reason I do
>> > >
>> > > unset SAGE_ROOT
>> > > unset SAGE_LOCAL
>> > >
>> > > before building any new release. I make sure current installed sagemath 
>> > > (in different folder) is not visible.
>> > >
>> > > --Nasser
>> > >
>> > > On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:
>> > >>
>> > >> 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 distclean" since 
>> > >> > everything is new.
>> > >> >
>> > >> > But I repeated now everything again using "make distclean" and got 
>> > >> > same error.
>> > >> >
>> > >> > "Probably the problem is linking with openblas. Do you have a number 
>> > >> > of openblas versions accessible to the linker?"
>> > >> >
>> > >> > I have no idea. What command should I use 

Re: [sage-release] Re: Sage 9.8.rc0 released

['Nasser M. Abbasi' via sage-release]

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)
libopenblas.so.3 => /usr/lib/libopenblas.so.3 (0x7f25a526)
libm.so.6 => /usr/lib/libm.so.6 (0x7f25a5178000)
libc.so.6 => /usr/lib/libc.so.6 (0x7f25a4f91000)
/usr/lib64/ld-linux-x86-64.so.2 (0x7f25a6a5b000)
libgomp.so.1 => /usr/lib/libgomp.so.1 (0x7f25a4f48000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f25a4f28000)
>

I've also put in same folder here   a 
file called log_folders.tar.gz  which is backup of the logs/ folder in my 
build tree of 9.8 rc0 so it will have the logs you asked for.

any other information needed please let me know.
--Nasser


On Sunday, February 5, 2023 at 4:17:44 AM UTC-6 Dima Pasechnik wrote:

> 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.cpython-310-x86_64-linux-gnu.so
> > > linux-vdso.so.1 (0x7ffc53be9000)
> > > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> > > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> > > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> > > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> > > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> > > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
> (0x7fc232444000)
> > > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
> >
> > here is how it looks on a non-broken installation.
> >
> > $ ldd 
> 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 (0x7ffe6b935000)
> > libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
> > libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
> > libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
> > libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
> > libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
> > libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
> > /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
> >
> > As you see, in your case libopenblas.so is not there, and you have an
> > error due to this.
> > Why scipy builds such a broken module, I don't know. I'd say it's a 
> scipy bug.
> >
> > Please post logs/pkgs/numpy* and logs/pkgs/scipy*
>
> please also check that
>
> ldd 
> local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_
> multiarray_umath.cpython-310-x86_64-linux-gnu.so
>
> has openblas in its output.
>
> >
> >
> > > >
> > >
> > > "You should add fpylll at the end of the line in
> > >
> > > build/pkgs/sagemath_doc_html/dependencies
> > >
> > > and run ./configure and make again"
> > >
> > > Ok thanks. Will give this a try.
> > >
> > > "sage in a different directory which is in your PATH typically breaks 
> things"
> > >
> > > but it is NOT in the path. This is the reason I do
> > >
> > > unset SAGE_ROOT
> > > unset SAGE_LOCAL
> > >
> > > before building any new release. I make sure current installed 
> sagemath (in different folder) is not visible.
> > >
> > > --Nasser
> > >
> > > On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:
> > >>
> > >> 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 distclean" since 
> everything is new.
> > >> >
> > >> > But I repeated now everything again using "make distclean" and got 
> same error.
> > >> >
> > >> > "Probably the problem is linking with openblas. Do you have a 
> number of openblas versions accessible to the linker?"
> > >> >
> > >> > I have no idea. What command should I use to check?
> > >>
> > >> run
> > >>
> > >> 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
> > >>
> > >> Post its output
> > >> - there should be an openblas mentioned, the question is which one.
> > >>
> > >> As far as fpylll is concerned, you've hit the bug fixed in not yet 
> merged
> > >> https://trac.sagemath.org/ticket/34940
> > >>
> > >> You should add fpylll at the end of the line in
> > >>
> > >> build/pkgs/sagemath_doc_html/dependencies
> > >>
> > >> and run ./configure and make 

Re: [sage-release] Re: Sage 9.8.rc0 released

[Dima Pasechnik]

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.cpython-310-x86_64-linux-gnu.so
> > linux-vdso.so.1 (0x7ffc53be9000)
> > libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> > libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> > libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> > libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> > libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> > libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
> > (0x7fc232444000)
> > /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>
> here is how it looks on a non-broken installation.
>
> $ ldd 
> 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 (0x7ffe6b935000)
> libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
> libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
> libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
> libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
> libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
> libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
> /lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)
>
> As you see, in your case libopenblas.so is not there, and you have an
> error due to this.
> Why scipy builds such a broken module, I don't know. I'd say it's a scipy bug.
>
> Please post logs/pkgs/numpy* and logs/pkgs/scipy*

please also check that

ldd 
local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/_multiarray_umath.cpython-310-x86_64-linux-gnu.so

has openblas in its output.

>
>
> > >
> >
> > "You should add fpylll at the end of the line in
> >
> > build/pkgs/sagemath_doc_html/dependencies
> >
> > and run ./configure and make again"
> >
> > Ok thanks. Will give this a try.
> >
> > "sage in a different directory which is in your PATH typically breaks 
> > things"
> >
> > but it is NOT in the path. This is the reason I do
> >
> > unset SAGE_ROOT
> >unset SAGE_LOCAL
> >
> > before building any new release. I make sure current installed sagemath (in 
> > different folder) is not visible.
> >
> > --Nasser
> >
> > On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> 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 distclean" since everything 
> >> > is new.
> >> >
> >> > But I repeated now everything again using "make distclean" and got same 
> >> > error.
> >> >
> >> > "Probably the problem is linking with openblas. Do you have a number of 
> >> > openblas versions accessible to the linker?"
> >> >
> >> > I have no idea. What command should I use to check?
> >>
> >> run
> >>
> >> 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
> >>
> >> Post its output
> >> - there should be an openblas mentioned, the question is which one.
> >>
> >> As far as fpylll is concerned, you've hit the bug fixed in not yet merged
> >> https://trac.sagemath.org/ticket/34940
> >>
> >> You should add fpylll at the end of the line in
> >>
> >> build/pkgs/sagemath_doc_html/dependencies
> >>
> >> and run ./configure and make again
> >>
> >>
> >>
> >>
> >> >
> >> > I am just following the instruction to download and install sagemath.
> >> >
> >> > I have giac and maxima and fricas and texlive already installed on this 
> >> > virtual box already. I also have sagemath 9.7 installed in different 
> >> > folder.
> >> >
> >> > --Nasser
> >> >
> >> >
> >> > On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
> >> >>
> >> >> 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-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so:
> >> >>  undefined symbol: dstevr_
> >> >>
> >> >> Probably the problem is linking with openblas. Do you have a number of 
> >> >> openblas versions accessible to the linker?
> >> 

Re: [sage-release] Re: Sage 9.8.rc0 released

[Dima Pasechnik]

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)
> libgfortran.so.5 => /usr/lib/libgfortran.so.5 (0x7fc232878000)
> libm.so.6 => /usr/lib/libm.so.6 (0x7fc23279)
> libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
> libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
> libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
> libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 (0x7fc232444000)
> /usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)

here is how it looks on a non-broken installation.

$ ldd 
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 (0x7ffe6b935000)
libopenblas.so.0 => /lib64/libopenblas.so.0 (0x7fe56140)
libgfortran.so.5 => /lib64/libgfortran.so.5 (0x7fe56100)
libm.so.6 => /lib64/libm.so.6 (0x7fe563865000)
libmvec.so.1 => /lib64/libmvec.so.1 (0x7fe561303000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7fe563845000)
libc.so.6 => /lib64/libc.so.6 (0x7fe560c0)
libquadmath.so.0 => /lib64/libquadmath.so.0 (0x7fe560fb8000)
/lib64/ld-linux-x86-64.so.2 (0x7fe563ad3000)

As you see, in your case libopenblas.so is not there, and you have an
error due to this.
Why scipy builds such a broken module, I don't know. I'd say it's a scipy bug.

Please post logs/pkgs/numpy* and logs/pkgs/scipy*


> >
>
> "You should add fpylll at the end of the line in
>
> build/pkgs/sagemath_doc_html/dependencies
>
> and run ./configure and make again"
>
> Ok thanks. Will give this a try.
>
> "sage in a different directory which is in your PATH typically breaks things"
>
> but it is NOT in the path. This is the reason I do
>
> unset SAGE_ROOT
>unset SAGE_LOCAL
>
> before building any new release. I make sure current installed sagemath (in 
> different folder) is not visible.
>
> --Nasser
>
> On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:
>>
>> 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 distclean" since everything 
>> > is new.
>> >
>> > But I repeated now everything again using "make distclean" and got same 
>> > error.
>> >
>> > "Probably the problem is linking with openblas. Do you have a number of 
>> > openblas versions accessible to the linker?"
>> >
>> > I have no idea. What command should I use to check?
>>
>> run
>>
>> 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
>>
>> Post its output
>> - there should be an openblas mentioned, the question is which one.
>>
>> As far as fpylll is concerned, you've hit the bug fixed in not yet merged
>> https://trac.sagemath.org/ticket/34940
>>
>> You should add fpylll at the end of the line in
>>
>> build/pkgs/sagemath_doc_html/dependencies
>>
>> and run ./configure and make again
>>
>>
>>
>>
>> >
>> > I am just following the instruction to download and install sagemath.
>> >
>> > I have giac and maxima and fricas and texlive already installed on this 
>> > virtual box already. I also have sagemath 9.7 installed in different 
>> > folder.
>> >
>> > --Nasser
>> >
>> >
>> > On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
>> >>
>> >> 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-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so:
>> >>  undefined symbol: dstevr_
>> >>
>> >> Probably the problem is linking with openblas. Do you have a number of 
>> >> openblas versions accessible to the linker?
>> >>
>> >>
>> >>
>> >> By the way,
>> >> what are you trying to achieve with exporting
>> >> MAXIMA ?
>> >> Sage does not support using external Maxima at the moment,
>> >>
>> >>
>> >>
>> >>
>> >> On Sat, 4 Feb 2023, 08:12 'Nasser M. Abbasi' via sage-release, 
>> >>  wrote:
>> >>>
>> >>> 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

Re: [sage-release] Re: Sage 9.8.rc0 released

['Nasser M. Abbasi' via sage-release]

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 => /usr/lib/libm.so.6 (0x7fc23279)
libmvec.so.1 => /usr/lib/libmvec.so.1 (0x7fc232696000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fc232676000)
libc.so.6 => /usr/lib/libc.so.6 (0x7fc23248f000)
libquadmath.so.0 => /usr/lib/../lib/libquadmath.so.0 
(0x7fc232444000)
/usr/lib64/ld-linux-x86-64.so.2 (0x7fc232ce1000)
>

"You should add fpylll at the end of the line in

build/pkgs/sagemath_doc_html/dependencies

and run ./configure and make again"

Ok thanks. Will give this a try.

"sage in a different directory which is in your PATH typically breaks 
things"

but it is NOT in the path. This is the reason I do 

unset SAGE_ROOT 
   unset SAGE_LOCAL 

before building any new release. I make sure current installed sagemath (in 
different folder) is not visible.

--Nasser

On Saturday, February 4, 2023 at 9:15:14 AM UTC-6 Dima Pasechnik wrote:

> 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 distclean" since everything is 
> new.
> >
> > But I repeated now everything again using "make distclean" and got same 
> error.
> >
> > "Probably the problem is linking with openblas. Do you have a number of 
> openblas versions accessible to the linker?"
> >
> > I have no idea. What command should I use to check?
>
> run
>
> 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
>
> Post its output
> - there should be an openblas mentioned, the question is which one.
>
> As far as fpylll is concerned, you've hit the bug fixed in not yet merged
> https://trac.sagemath.org/ticket/34940
>
> You should add fpylll at the end of the line in
>
> build/pkgs/sagemath_doc_html/dependencies
>
> and run ./configure and make again
>
>
>
>
> >
> > I am just following the instruction to download and install sagemath.
> >
> > I have giac and maxima and fricas and texlive already installed on this 
> virtual box already. I also have sagemath 9.7 installed in different folder.
> >
> > --Nasser
> >
> >
> > On Saturday, February 4, 2023 at 5:27:59 AM UTC-6 Dima Pasechnik wrote:
> >>
> >> 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-python3.10/lib/python3.10/site-packages/scipy/special/_
> ufuncs.cpython-310-x86_64-linux-gnu.so: undefined symbol: dstevr_
> >>
> >> Probably the problem is linking with openblas. Do you have a number of 
> openblas versions accessible to the linker?
> >>
> >>
> >>
> >> By the way,
> >> what are you trying to achieve with exporting
> >> MAXIMA ?
> >> Sage does not support using external Maxima at the moment,
> >>
> >>
> >>
> >>
> >> On Sat, 4 Feb 2023, 08:12 'Nasser M. Abbasi' via sage-release, <
> sage-r...@googlegroups.com> wrote:
> >>>
> >>> 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=/usr/local/bin/giac
> >>> export MAXIMA=/usr/local/bin/maxima
> >>> ./configure --with-system-python=no
> >>> make
> >>>
> >>> At the end I see
> >>>
> >>> -
> >>> sagemath_doc_html-none] File 
> "/home/me/TMP/sage-9.8.rc0/src/sage_docbuild/sphinxbuild.py", line 263, in 
> raise_errors
> >>> [sagemath_doc_html-none] raise OSError(self._error)
> >>> [sagemath_doc_html-none] OSError: 
> /home/me/TMP/sage-9.8.rc0/src/sage/manifolds/chart.py:docstring of 
> sage.manifolds.chart.RealChart.plot:104: WARNING: Exception occurred in 
> plotting chart-1
> >>> [sagemath_doc_html-none]
> >>> [sagemath_doc_html-none] Note: incremental documentation builds 
> sometimes cause spurious
> >>> [sagemath_doc_html-none] error messages. To be certain that these are 
> real errors, run
> >>> [sagemath_doc_html-none] "make doc-clean doc-uninstall" first and try 
> again.
> >>> [sagemath_doc_html-none] make[6]: *** [Makefile:28: 
> doc-inventory--reference-manifolds] Error 1
> >>> [sagemath_doc_html-none] make[5]: *** [Makefile:45: 
>