Re: [sage-release] Sage 10.4.beta6 released

I see the same failure od fflas_ffpack on macOS 14.1. - Marc On Monday, May 13, 2024 at 5:53:22 AM UTC-5 david@gmail.com wrote: > I’m unable to compile on macOS 12.7.4 on a fresh clone (and fresh shell). > > The compilation of fflas_ffpack-2.5.0 is failing. See attached log. > > -- You

Re: [sage-release] A detail that matters - please help

No, that is not correct. The fundamental issue is the size of the compressed file. And this is an issue with documentation, not with arbitrary graphics. The matplotlib images in the Sage documentation do not involve millions of lines of svg code. The svg files are small to start with and

Re: [sage-release] A detail that matters - please help

t; happen? I guess there is a lot of files that would be involved in the > transition. > > Vincent > > On Wed, 28 Jun 2023 at 16:23, Marc Culler wrote: > > > > Details really do matter. The devil is in them. Here is one which makes > a major difference to my efforts t

[sage-release] A detail that matters - please help

Details really do matter. The devil is in them. Here is one which makes a major difference to my efforts to distribute Sage. I hope that I can convince people to pay attention to it. DETAIL: An svg image can be compressed very efficiently and will look good at all resolutions. A png image

[sage-release] Re: Sage 10.1.beta4 released

I have resolved my problem with building the documentation, and I now understand why no one could help me with it. Thanks. - Marc On Sunday, June 25, 2023 at 5:07:17 PM UTC-5 Marc Culler wrote: > I can get the documentation to build if I modify sphinxbuild.py to make it >

[sage-release] Re: Sage 10.1.beta4 released

be in [manifolds]. When the inventory warning is ignored the object.inv files do in fact get built later, and they get installed in the correct place. - Marc On Sunday, June 25, 2023 at 2:21:05 PM UTC-5 Marc Culler wrote: > I am not able to build the documentation for 10.1beta4 on macOS. > &

[sage-release] Re: Sage 10.1.beta4 released

I am not able to build the documentation for 10.1beta4 on macOS. First, there are inconsistent paths for the file references/objects.inv. At different times it is expected to be in two different places: local/share/doc/sage/inventory/en/reference/references/objects.inv

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

While preparing a binary release for macOS I discovered that in 10.0.rc1 the gap-packages spkg fails to install the script BuildPackages.sh in sage/local/lib/gap/bin. This breaks installation of GAP packages with libgap.InstallPackage. All that needs to be done to fix it is to copy that

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

a Pasechnik, wrote: > >> does >> >> sage: libgap.LoadPackage("semigroup") >> >> crash, as well? >> >> and how about the same at GAP prompt: >> >> ./sage --gap >> .. >> >>gap> LoadPackage("semigroup&quo

[sage-release] Re: Sage 9.8 released

By running the load command in sage -gap I can see that GAP is crashing with an illegal instruction error while trying to load the semigroups package. - Marc On Sunday, February 19, 2023 at 10:04:51 AM UTC-6 Marc Culler wrote: > I am trying to build the binary release of Sage 9.8 for ma

[sage-release] Re: Sage 9.8 released

I am trying to build the binary release of Sage 9.8 for macOS and I have run into a mysterious problem. I wonder if anyone on this list has any insight into it. There are really two separate binary releases: one for Intel and one for Apple Silicon. These are built using the same build script

Re: [sage-release] Sage 9.7.beta8 released

This is fixed in ticket #34221 . Cython 2.9 does not find .pxd files in directories which do not contain an __init__.py file, and the __init__.py files were removed from several directories by ticket #33011 . The

[sage-release] Re: Sage 9.7.beta5 released

I used sed to fix the 16 files with bad shebangs in sage/venv-python3.10.5/bin and that appeared to produce a working copy of sage. So perhaps the bad shebangs are the only reason that venv-python3.10.5 depends on venv-python3.10.3. - Marc On Thursday, July 14, 2022 at 7:30:47 AM UTC-5 Marc

[sage-release] Re: Sage 9.7.beta5 released

I don't want to have to remember to do this by hand. If I delete all of the venvs before starting an incremental build will the build still work, and will it create a new venv that is appropriate for its python, even if the python version has not changed? - Marc On Wednesday, July 13, 2022

[sage-release] Re: Sage 9.7.beta5 released

That statement is actually false. I think this issue needs to be addressed. I think the old venvs should be removed when doing an incremental build, since I cannot think of any use for them. Here is the problem. When I did an incremental build with the venv-python3.10.3 in place, a new venv

[sage-release] Re: Sage 9.7.beta5 released

After working around the issues with the bootstrap script and symengine_py I have managed to build 9.7.beta5 on an arm mac mini. This was an incremental build from beta4. When the build finished I noticed that both sage/local/var/lib/sage/venv-python3.10.3 and

Re: [sage-release] Re: Sage 9.7.beta5 released

On Mon, Jul 11, 2022 at 10:01 AM Dima Pasechnik wrote: > > One way to fix it is to re-create ./configure from ./bootstrap > The problem with this is that the bootstrap script in beta5 generates warnings about the exact same commands, but then it still goes ahead and produces a configure script

Re: [sage-release] Re: Sage 9.7.beta5 released

gettext was silently removed from the list of bootstrap packages for beta5, which is clearly not a good idea. - Marc - Marc On Mon, Jul 11, 2022 at 9:08 AM Dima Pasechnik wrote: > On Mon, Jul 11, 2022 at 2:21 PM Marc Culler wrote: > > > > Yes, I tried that but ther

Re: [sage-release] Re: Sage 9.7.beta5 released

build. > > > 2022年7月11日(月) 15:21 Marc Culler : > >> Yes, I tried that but there was no change. >> >> However when I deleted the calls to the undefined autoconf commands from >> the configure script (which meant changing about 5 lines in the script) I >> was

Re: [sage-release] Re: Sage 9.7.beta5 released

On Monday, July 11, 2022 at 7:11:21 AM UTC-5 Dima Pasechnik wrote: > > did you run > ./bootstrap > ? > On Mon, 11 Jul 2022, 13:08 Marc Culler, wrote: > >> I am not able to build beta5 after running make distclean using my >> standard build script that includes

[sage-release] Re: Sage 9.7.beta5 released

I am not able to build beta5 after running make distclean using my standard build script that includes no external libraries. I am seeing errors about missing autoconf commands: make: `configure' is up to date. ./configure: line 4932: AC_LIB_RPATH: command not found ./configure: line 24924:

[sage-release] Re: Sage 9.7.beta4 released

When I tried to build 9.7.beta4 on an M1 mac mini with macOS 12.4 using no external libraries except the Homebrew gfortran I got this error: * error: Multiple top-level packages discovered in a flat-layout: ['cmake', 'symengine']. To avoid accidental inclusion of unwanted files or

Re: [sage-release] Re: Sage 9.5.rc2 release

ith that. >> >> I also added a copy of the gfortran runtime, suitably adjusted to work in >> the Sage framework in the app bundle. >> >> Matthias, I think you should revise your recommendation so it specifies >> the homebrew gfortran-11. >> On Monday, January 17,

[sage-release] Re: Sage 9.5.rc2 release

in the Sage framework in the app bundle. Matthias, I think you should revise your recommendation so it specifies the homebrew gfortran-11. On Monday, January 17, 2022 at 3:13:38 PM UTC-6 Marc Culler wrote: > My attempt to build rc2 on macOS with arm CPU failed with this error: > > I

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

as root and I also tried adding debugger entitlements and resigning the >>>> app. Neither make it possible for me to use lldb on sage itself. >>>> >>>> I am able to start the sage python3 in lldb. If I knew how to import >>>> the Manifold class from pyth

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

d >> I get a python exception whose traceback ends with: >> File "sage/structure/category_object.pyx", line 60, in init >> sage.structure.category_object >> (build/cythonized/sage/structure/category_object.c:9914) >> ImportError: cannot import name Catego

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

e sage python3 in lldb. If I knew how to import the >> Manifold class from python I might be able to get somewhere. But if I run >> >>> from sage.manifolds import manifold >> I get a python exception whose traceback ends with: >> File "sage/structure/catego

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

I was able to get a bit further in python by running: >>> from sage.structure import * Then when I tried >>> from sage.manifolds import manifold I get an exception whose traceback ends with AttributeError: module 'sage.structure' has no attribute 'sage_object' This seems strange, since there

[sage-release] Re: Sage 9.5.rc2 release

Adding $(PYTHON_TOOLCHAIN) to the cryptominisat dependencies fixed the build failure that I encountered. On Sunday, January 16, 2022 at 4:09:02 PM UTC-6 matthia...@gmail.com wrote: > The sqlite doctest failure is tracked at > https://trac.sagemath.org/ticket/29092 > > On Sunday, January 16,

[sage-release] Re: Sage 9.5.rc2 release

My attempt to build rc2 on macOS with arm CPU failed with this error: Installing cryptominisat-5.6.8 /private/var/tmp/sage-9.5-current/local/var/lib/sage/venv-python3.9.9/bin/python3: No module named pip Maybe a pip dependency is missing now for cryptominisat? - Marc On Sunday, January 16,

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

ImportError: cannot import name Category - Marc On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote: > Hi Matthias, > > I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs > at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1. >

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

Hi Matthias, I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1. There are two separate disk images. You may recall that I do not use Homebrew or Conda, but I did have to use an experimental binary