you need

     make cython-clean cython-uninstall


to trigger the rebuild of Cython by

     make cython

On Mon, 16 Oct 2023, 21:57 Dima Pasechnik, <dimp...@gmail.com> wrote:

> for me, the beginning of logs/pkgs/cython-3.0.2.log
> on the branch of PR 36332
> is as follows. You see, the patch is applied.
>
>
> Attempting to download package Cython-3.0.2.tar.gz from mirrors
>
> https://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/cython/Cython-3.0.2.tar.gz
> [......................................................................]
> cython-3.0.2
> ====================================================
> Setting up build directory for cython-3.0.2
> Finished extraction
> Applying patches from ../patches...
> Applying ../patches/5690.patch
> patching file Cython/Debugger/DebugWriter.py
> ****************************************************
>
> Why it's not like this for you, I have no idea.
>
> On Mon, Oct 16, 2023 at 9:54 PM Emmanuel Charpentier
> <emanuel.charpent...@gmail.com> wrote:
> >
> > Le lundi 16 octobre 2023 à 22:41:38 UTC+2, Dima Pasechnik a écrit :
> >
> > can you check that build/pkgs/cython/patches/5690.patch is there?
> >
> > Indeed it is here…
> >
> > charpent@zen-book-flip:/usr/local/sage-10$ ls
> build/pkgs/cython/patches/ 5690.patch
> >
> > And make build still fails :
> >
> > [sagelib-10.2.beta7] [143/144] Cythonizing sage/symbolic/expression.pyx
> [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback:
> [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call
> last): [sagelib-10.2.beta7] File
> "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker
> [sagelib-10.2.beta7] result = (True, func(*args, **kwds))
> [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File
> "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar
> [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7]
> ^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
> line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return
> cythonize_one(*m) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^
> [sagelib-10.2.beta7] File
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
> line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None,
> pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError:
> sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
> [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The
> above exception was the direct cause of the following exception:
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call
> last): [sagelib-10.2.beta7] File "<string>", line 2, in <module>
> [sagelib-10.2.beta7] File "<pip-setuptools-caller>", line 34, in <module>
> [sagelib-10.2.beta7] File "/usr/local/sage-10/src/setup.py", line 108, in
> <module> [sagelib-10.2.beta7] extensions = cythonize( [sagelib-10.2.beta7]
> ^^^^^^^^^^ [sagelib-10.2.beta7] File
> "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py",
> line 1125, in cythonize [sagelib-10.2.beta7] result.get(99999) # seconds
> [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File
> "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get
> [sagelib-10.2.beta7] raise self._value [sagelib-10.2.beta7]
> Cython.Compiler.Errors.CompileError:
> sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx
> [sagelib-10.2.beta7]
> ************************************************************************
> [sagelib-10.2.beta7] Error building the Sage library [sagelib-10.2.beta7]
> ************************************************************************
> [sagelib-10.2.beta7] Please email sage-devel (
> http://groups.google.com/group/sage-devel) [sagelib-10.2.beta7]
> explaining the problem and including the relevant part of the log file
> [sagelib-10.2.beta7] /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log
> [sagelib-10.2.beta7] Describe your computer, operating system, etc.
> [sagelib-10.2.beta7]
> ************************************************************************
> [sagelib-10.2.beta7] error: subprocess-exited-with-error
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not
> run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7]
> ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note:
> This error originates from a subprocess, and is likely not a problem with
> pip. [sagelib-10.2.beta7] full command:
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 -c '
> [sagelib-10.2.beta7] exec(compile('"'"''"'"''"'"' [sagelib-10.2.beta7] #
> This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
> [sagelib-10.2.beta7] # [sagelib-10.2.beta7] # - It imports setuptools
> before invoking setup.py, to enable projects that directly
> [sagelib-10.2.beta7] # import from `distutils.core` to work with newer
> packaging standards. [sagelib-10.2.beta7] # - It provides a clear error
> message when setuptools is not installed. [sagelib-10.2.beta7] # - It sets
> `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
> [sagelib-10.2.beta7] # setuptools doesn'"'"'t think the script is `-c`.
> This avoids the following warning: [sagelib-10.2.beta7] # manifest_maker:
> standard file '"'"'-c'"'"' not found". [sagelib-10.2.beta7] # - It
> generates a shim setup.py, for handling setup.cfg-only projects.
> [sagelib-10.2.beta7] import os, sys, tokenize [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] try: [sagelib-10.2.beta7] import setuptools
> [sagelib-10.2.beta7] except ImportError as error: [sagelib-10.2.beta7]
> print( [sagelib-10.2.beta7] "ERROR: Can not execute `setup.py` since
> setuptools is not available in " [sagelib-10.2.beta7] "the build
> environment.", [sagelib-10.2.beta7] file=sys.stderr, [sagelib-10.2.beta7] )
> [sagelib-10.2.beta7] sys.exit(1) [sagelib-10.2.beta7] [sagelib-10.2.beta7]
> __file__ = %r [sagelib-10.2.beta7] sys.argv[0] = __file__
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] if os.path.exists(__file__):
> [sagelib-10.2.beta7] filename = __file__ [sagelib-10.2.beta7] with
> tokenize.open(__file__) as f: [sagelib-10.2.beta7] setup_py_code = f.read()
> [sagelib-10.2.beta7] else: [sagelib-10.2.beta7] filename = "<auto-generated
> setuptools caller>" [sagelib-10.2.beta7] setup_py_code = "from setuptools
> import setup; setup()" [sagelib-10.2.beta7] [sagelib-10.2.beta7]
> exec(compile(setup_py_code, filename, "exec")) [sagelib-10.2.beta7]
> '"'"''"'"''"'"' % ('"'"'/usr/local/sage-10/src/setup.py'"'"',),
> "<pip-setuptools-caller>", "exec"))' --no-user-cfg develop --no-deps
> [sagelib-10.2.beta7] cwd: /usr/local/sage-10/src/ [sagelib-10.2.beta7]
> Rolling back uninstall of sagemath-standard [sagelib-10.2.beta7] Moving to
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/sagemath-standard.egg-link
> [sagelib-10.2.beta7] from
> /tmp/pip-uninstall-x35mufkn/sagemath-standard.egg-link [sagelib-10.2.beta7]
> error: subprocess-exited-with-error [sagelib-10.2.beta7]
> [sagelib-10.2.beta7] × python setup.py develop did not run successfully.
> [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for
> output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error
> originates from a subprocess, and is likely not a problem with pip.
> [sagelib-10.2.beta7]
> ********************************************************************************
> [sagelib-10.2.beta7] Error installing [sagelib-10.2.beta7]
> ********************************************************************************
> [sagelib-10.2.beta7] [sagelib-10.2.beta7] real 1m8,293s
> [sagelib-10.2.beta7] user 3m46,560s [sagelib-10.2.beta7] sys 0m9,187s
> make[4]: *** [Makefile:3373 : sagelib-SAGE_VENV-no-deps] Erreur 1 make[3]:
> *** [Makefile:3373 :
> /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/installed/sagelib-10.2.beta7]
> Erreur 2 make[2]: *** [Makefile:2849 : all-build] Erreur 2 make[2] : on
> quitte le répertoire « /usr/local/sage-10/build/make » real 1m8,804s user
> 3m51,007s sys 0m14,169s
> *************************************************************** Error
> building Sage. The following package(s) may have failed to build (not
> necessarily during this run of 'make all-build'): * package:
> sagelib-10.2.beta7 last build time: 16 oct. 22:42 log file:
> /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log It is safe to delete
> any log files and build directories, but they contain information that is
> helpful for debugging build problems. WARNING: If you now run 'make' again,
> the build directory of the same version of the package will, by default, be
> deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent
> this. make[1]: *** [Makefile:40 : all-build] Erreur 1 make[1] : on quitte
> le répertoire « /usr/local/sage-10 » make: *** [Makefile:16 : build] Erreur
> 2 real 1m9,904s user 3m52,308s sys 0m15,791s
> >
> >
> >
> > On Mon, Oct 16, 2023 at 9:38 PM Emmanuel Charpentier
> > <emanuel.c...@gmail.com> wrote:
> > >
> > > Le lundi 16 octobre 2023 à 22:31:38 UTC+2, Emmanuel Charpentier a
> écrit :
> > >
> > > Le lundi 16 octobre 2023 à 18:35:28 UTC+2, Dima Pasechnik a écrit :
> > >
> > > On Mon, Oct 16, 2023 at 5:29 PM Dima Pasechnik <dim...@gmail.com>
> wrote:
> > > >
> > > > Please also send config.log, as I already asked.
> > >
> > > Done. See above
> > >
> > >
> > > >
> > > > On Mon, Oct 16, 2023 at 5:27 PM <emanuel.c...@gmail.com> wrote:
> > > > >
> > > > > IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log
> > >
> > > It looks as if you haven't installed the patch for Cython, as I still
> see
> > >
> > > ValueError: Invalid tag name '.0'
> > >
> > > in your log.
> > >
> > > You can check this somewhere in the beginning of
> logs/pkgs/cython*...log
> > > You'd see there "applying patch <such and such>"
> > >
> > > Indeed :
> > >
> > > charpent@zen-book-flip:/usr/local/sage-10$ grep patch
> logs/pkgs/cython-3.0.2.log No patch files found in ../patches
> > >
> > > However, I’m pretty certain to have run it (but it has already
> scrolled off my session transcript) .
> > >
> > > I’ll try to start again :
> > >
> > > - make sagelib-clean sagelib uninstall - git pull upstream
> pull/36332/head
> > >
> > > BTW :
> > >
> > > charpent@zen-book-flip:/usr/local/sage-10$ git pull upstream
> pull/36332/head Depuis github.com:sagemath/sage * branch
> refs/pull/36332/head -> FETCH_HEAD Déjà à jour.
> > >
> > > (“already up to date”).
> > >
> > > - make cython - make build
> > >
> > >
> > >
> > >
> > > > >
> > > > > Here it is.
> > > > >
> > > > > --
> > > > > 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...@googlegroups.com.
> > > > > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/3210ca421c3720605652da6ca86165e187c64ccd.camel%40gmail.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...@googlegroups.com.
> > > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/9bba3b91-09c9-40f0-8945-9d5c7a3c5b24n%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/ace78125-2f11-4ce6-bf9f-71f88f999057n%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/CAAWYfq0yrsDNXU1xGbtLcsyEapSoJSvV3ShK%3Dpu2%3DXHu2mvZrg%40mail.gmail.com.

Reply via email to