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

2023-02-02 Thread Sébastien Labbé


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?
 

It returns nothing! Thanks for the hint. I found the problem: when reading 
the sage README to install sage from scratch on this new machine, I 
installed the basic stuff as follows:

$ sudo apt install gcc gfortran g++ make m4 perl ranlib tar bc
[...]
E: Impossible de trouver le paquet ranlib

But this returned an error on ranlib and I assumed it had installed the 
other packages in the list but no, it did not (gcc, gfortran, etc. were not 
installed as well).

Is ranlib really needed for sage? Can we remove it from the README?



-- 
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/d6aecaee-279a-45f8-a645-36483d72a382n%40googlegroups.com.


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

2023-02-02 Thread Matthias Köppe
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-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/0aac31a1-e96e-4f1b-95e1-10fb581368dcn%40googlegroups.com.


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

2023-02-02 Thread Dima Pasechnik
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, or m4 is not
installed.

Or it's a bug that slipped in due to insufficient testing on machines
without installed autotools.


Never done that before...
>
> See below:
>
> $ make configure
> ./bootstrap -d
> make[1] : on entre dans le répertoire « /home/slabbe/GitBox/sage »
> rm -rf config/install-sh config/compile config/config.guess
> config/config.sub config/missing configure build/make/Makefile-auto.in
> rm -f src/doc/en/installation/*.txt
> rm -rf src/doc/en/reference/spkg/*.rst
> rm -f environment.yml
> rm -f src/environment.yml
> rm -f src/environment-dev.yml
> rm -f environment-optional.yml
> rm -f src/environment-optional.yml
> rm -f src/Pipfile
> rm -f src/pyproject.toml
> rm -f src/requirements.txt
> rm -f src/setup.cfg
> make[1] : on quitte le répertoire « /home/slabbe/GitBox/sage »
> bootstrap:: installing 'm4/sage_spkg_configures.m4'
> ./bootstrap: installing
> /home/slabbe/GitBox/sage/build/pkgs/sagemath_environment/src/pyproject.toml
> ./bootstrap: 9: m4: Permission denied
> make: *** [Makefile:365 : configure] Erreur 1
>
> --
> 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/3005af48-d9e6-4399-9575-1ac642258308n%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/CAAWYfq15wgr0gWT1T4srb-48hn-URJrHtjpAuD0-EYHLBTMpdQ%40mail.gmail.com.


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

2023-02-02 Thread Sébastien Labbé
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 Singular that has had many isses, but last time I checked, it had a 
positive review and was marked a blocker.

Thanks for the reply.  Well, I am experiencing the issue on the old Ubuntu 
18.04 on which singular is not installed :

$ singular
singular : commande introuvable

I already tried "--with-system-singular=no" last week after reading the 
previous post, but I still have the same issue. I am currently trying again 
with rc0 and after make distclean just to make sure.

Sébastien


 

-- 
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/097ef1f3-82ca-4c55-b04b-25a002f8fb52n%40googlegroups.com.


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

2023-02-02 Thread John H Palmieri
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 
positive review and was marked a blocker.

On Thursday, February 2, 2023 at 7:32:20 AM UTC-8 Sébastien Labbé wrote:

> 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/sage/logs/pkgs/sagelib-9.8.rc0.log
>   [sagelib-9.8.rc0] error installing, exit status 1. End of log file:
>   [sagelib-9.8.rc0] | 
> ^~
>   [sagelib-9.8.rc0]   sage/misc/nested_class.c:1341:43: note: in 
> expansion of macro ‘__Pyx_TRASHCAN_BEGIN_CONDITION’
>   [sagelib-9.8.rc0]1341 | #define __Pyx_TRASHCAN_BEGIN(op, 
> dealloc) __Pyx_TRASHCAN_BEGIN_CONDITION(op,\
>   [sagelib-9.8.rc0] | 
>   ^~
>   [sagelib-9.8.rc0]   sage/misc/nested_class.c:2680:3: note: in 
> expansion of macro ‘__Pyx_TRASHCAN_BEGIN’
>   [sagelib-9.8.rc0]2680 |   __Pyx_TRASHCAN_BEGIN(o, 
> __pyx_tp_dealloc_4sage_4misc_12nested_class_NestedClassMetaclass)
>   [sagelib-9.8.rc0] |   ^~~~
>   [sagelib-9.8.rc0]   sage/misc/nested_class.c:1338:17: warning: 
> implicit declaration of function ‘_PyTrash_thread_destroy_chain’ 
> [-Wimplicit-function-declaration]
>   [sagelib-9.8.rc0]1338 | 
> _PyTrash_thread_destroy_chain();\
>   [sagelib-9.8.rc0] | 
> ^
>   [sagelib-9.8.rc0]   sage/misc/nested_class.c:2683:3: note: in 
> expansion of macro ‘__Pyx_TRASHCAN_END’
>   [sagelib-9.8.rc0]2683 |   __Pyx_TRASHCAN_END
>   [sagelib-9.8.rc0] |   ^~
>   [sagelib-9.8.rc0]   error: Command "gcc-9 -Wsign-compare -DNDEBUG -g 
> -fwrapv -O3 -Wall -Wno-unused -g -O2 -g -O2 -fPIC 
> -I/home/slabbe/GitBox/sage/src 
> -I/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/numpy/core/include
>  
> -I/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/include/python3.11
>  
> -I/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/include/python3.11
>  
> -c sage/categories/category_cy_helper.c -o 
> build/temp.linux-x86_64-cpython-311/sage/categories/category_cy_helper.o" 
> failed with exit status 1
>   [sagelib-9.8.rc0]   error: subprocess-exited-with-error
>   [sagelib-9.8.rc0]   
>   [sagelib-9.8.rc0]   × python setup.py develop did not run 
> successfully.
>   [sagelib-9.8.rc0]   │ exit code: 1
>   [sagelib-9.8.rc0]   ╰─> See above for output.
>   [sagelib-9.8.rc0]   
>   [sagelib-9.8.rc0]   note: This error originates from a subprocess, 
> and is likely not a problem with pip.
>   [sagelib-9.8.rc0]   full command: 
> /home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/bin/python3 
> -c '
>   [sagelib-9.8.rc0]   exec(compile('"'"''"'"''"'"'
>   [sagelib-9.8.rc0]   # This is  -- a caller 
> that pip uses to run setup.py
>   [sagelib-9.8.rc0]   #
>   [sagelib-9.8.rc0]   # - It imports setuptools before invoking 
> setup.py, to enable projects that directly
>   [sagelib-9.8.rc0]   #   import from `distutils.core` to work with 
> newer packaging standards.
>   [sagelib-9.8.rc0]   # - It provides a clear error message when 
> setuptools is not installed.
>   [sagelib-9.8.rc0]   # - It sets `sys.argv[0]` to the underlying 
> `setup.py`, when invoking `setup.py` so
>   [sagelib-9.8.rc0]   #   setuptools doesn'"'"'t think the script is 
> `-c`. This avoids the following warning:
>   [sagelib-9.8.rc0]   # manifest_maker: standard file '"'"'-c'"'"' 
> not found".
>   [sagelib-9.8.rc0]   # - It generates a shim setup.py, for handling 
> setup.cfg-only projects.
>   [sagelib-9.8.rc0]   import os, sys, tokenize
>   [sagelib-9.8.rc0]   
>   [sagelib-9.8.rc0]   try:
>   [sagelib-9.8.rc0]   import setuptools
>   [sagelib-9.8.rc0]   except ImportError as error:
>   [sagelib-9.8.rc0]   print(
>   [sagelib-9.8.rc0]   "ERROR: Can not execute `setup.py` since 
> setuptools is not available in "
>   [sagelib-9.8.rc0]   "the build environment.",
>   [sagelib-9.8.rc0]   file=sys.stderr,
>   [sagelib-9.8.rc0]   )
>   [sagelib-9.8.rc0]   sys.exit(1)
>   [sagelib-9.8.rc0]   
>   [sagelib-9.8.rc0]   __file__ = %r
>   [sagelib-9.8.rc0]   sys.argv[0] = __file__
>   [sagelib-9.8.rc0]   
>   [sagelib-9.8.rc0]   if 

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

2023-02-02 Thread Sébastien Labbé
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/slabbe/GitBox/sage »
rm -rf config/install-sh config/compile config/config.guess 
config/config.sub config/missing configure build/make/Makefile-auto.in
rm -f src/doc/en/installation/*.txt
rm -rf src/doc/en/reference/spkg/*.rst
rm -f environment.yml
rm -f src/environment.yml
rm -f src/environment-dev.yml
rm -f environment-optional.yml
rm -f src/environment-optional.yml
rm -f src/Pipfile
rm -f src/pyproject.toml
rm -f src/requirements.txt
rm -f src/setup.cfg
make[1] : on quitte le répertoire « /home/slabbe/GitBox/sage »
bootstrap:: installing 'm4/sage_spkg_configures.m4'
./bootstrap: installing 
/home/slabbe/GitBox/sage/build/pkgs/sagemath_environment/src/pyproject.toml
./bootstrap: 9: m4: Permission denied
make: *** [Makefile:365 : configure] Erreur 1

-- 
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/3005af48-d9e6-4399-9575-1ac642258308n%40googlegroups.com.


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

2023-02-02 Thread Sébastien Labbé
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/sage/logs/pkgs/sagelib-9.8.rc0.log
  [sagelib-9.8.rc0] error installing, exit status 1. End of log file:
  [sagelib-9.8.rc0] | 
^~
  [sagelib-9.8.rc0]   sage/misc/nested_class.c:1341:43: note: in 
expansion of macro ‘__Pyx_TRASHCAN_BEGIN_CONDITION’
  [sagelib-9.8.rc0]1341 | #define __Pyx_TRASHCAN_BEGIN(op, dealloc) 
__Pyx_TRASHCAN_BEGIN_CONDITION(op,\
  [sagelib-9.8.rc0] |   
^~
  [sagelib-9.8.rc0]   sage/misc/nested_class.c:2680:3: note: in 
expansion of macro ‘__Pyx_TRASHCAN_BEGIN’
  [sagelib-9.8.rc0]2680 |   __Pyx_TRASHCAN_BEGIN(o, 
__pyx_tp_dealloc_4sage_4misc_12nested_class_NestedClassMetaclass)
  [sagelib-9.8.rc0] |   ^~~~
  [sagelib-9.8.rc0]   sage/misc/nested_class.c:1338:17: warning: 
implicit declaration of function ‘_PyTrash_thread_destroy_chain’ 
[-Wimplicit-function-declaration]
  [sagelib-9.8.rc0]1338 | 
_PyTrash_thread_destroy_chain();\
  [sagelib-9.8.rc0] | 
^
  [sagelib-9.8.rc0]   sage/misc/nested_class.c:2683:3: note: in 
expansion of macro ‘__Pyx_TRASHCAN_END’
  [sagelib-9.8.rc0]2683 |   __Pyx_TRASHCAN_END
  [sagelib-9.8.rc0] |   ^~
  [sagelib-9.8.rc0]   error: Command "gcc-9 -Wsign-compare -DNDEBUG -g 
-fwrapv -O3 -Wall -Wno-unused -g -O2 -g -O2 -fPIC 
-I/home/slabbe/GitBox/sage/src 
-I/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/numpy/core/include
 
-I/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/include/python3.11
 
-I/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/include/python3.11
 
-c sage/categories/category_cy_helper.c -o 
build/temp.linux-x86_64-cpython-311/sage/categories/category_cy_helper.o" 
failed with exit status 1
  [sagelib-9.8.rc0]   error: subprocess-exited-with-error
  [sagelib-9.8.rc0]   
  [sagelib-9.8.rc0]   × python setup.py develop did not run 
successfully.
  [sagelib-9.8.rc0]   │ exit code: 1
  [sagelib-9.8.rc0]   ╰─> See above for output.
  [sagelib-9.8.rc0]   
  [sagelib-9.8.rc0]   note: This error originates from a subprocess, 
and is likely not a problem with pip.
  [sagelib-9.8.rc0]   full command: 
/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.1/bin/python3 
-c '
  [sagelib-9.8.rc0]   exec(compile('"'"''"'"''"'"'
  [sagelib-9.8.rc0]   # This is  -- a caller 
that pip uses to run setup.py
  [sagelib-9.8.rc0]   #
  [sagelib-9.8.rc0]   # - It imports setuptools before invoking 
setup.py, to enable projects that directly
  [sagelib-9.8.rc0]   #   import from `distutils.core` to work with 
newer packaging standards.
  [sagelib-9.8.rc0]   # - It provides a clear error message when 
setuptools is not installed.
  [sagelib-9.8.rc0]   # - It sets `sys.argv[0]` to the underlying 
`setup.py`, when invoking `setup.py` so
  [sagelib-9.8.rc0]   #   setuptools doesn'"'"'t think the script is 
`-c`. This avoids the following warning:
  [sagelib-9.8.rc0]   # manifest_maker: standard file '"'"'-c'"'"' 
not found".
  [sagelib-9.8.rc0]   # - It generates a shim setup.py, for handling 
setup.cfg-only projects.
  [sagelib-9.8.rc0]   import os, sys, tokenize
  [sagelib-9.8.rc0]   
  [sagelib-9.8.rc0]   try:
  [sagelib-9.8.rc0]   import setuptools
  [sagelib-9.8.rc0]   except ImportError as error:
  [sagelib-9.8.rc0]   print(
  [sagelib-9.8.rc0]   "ERROR: Can not execute `setup.py` since 
setuptools is not available in "
  [sagelib-9.8.rc0]   "the build environment.",
  [sagelib-9.8.rc0]   file=sys.stderr,
  [sagelib-9.8.rc0]   )
  [sagelib-9.8.rc0]   sys.exit(1)
  [sagelib-9.8.rc0]   
  [sagelib-9.8.rc0]   __file__ = %r
  [sagelib-9.8.rc0]   sys.argv[0] = __file__
  [sagelib-9.8.rc0]   
  [sagelib-9.8.rc0]   if os.path.exists(__file__):
  [sagelib-9.8.rc0]   filename = __file__
  [sagelib-9.8.rc0]   with tokenize.open(__file__) as f:
  [sagelib-9.8.rc0]   setup_py_code = f.read()
  [sagelib-9.8.rc0]   else:
  [sagelib-9.8.rc0]   filename = ""
  [sagelib-9.8.rc0]   setup_py_code = "from setuptools import 
setup; setup()"
  [sagelib-9.8.rc0]   
  [sagelib-9.8.rc0]   exec(compile(setup_py_code, filename, "exec"))
  [sagelib-9.8.rc0]   '"'"''"'"''"'"' % 
('"'"'/home/slabbe/GitBox/sage/src/setup.py'"'"',), 
"", "exec"))' --no-user-cfg develop --no-deps