There are other problems in the documentation related to building from source, which could be added to this ticket. I noticed them as I recently tried to build from source from scratch.
The suggested commands on the page you mentioned are: [user@localhost ~]$ git clone https://gitlab.com/sagemath/dev/tracmirror.git [user@localhost ~]$ cd sage [user@localhost sage]$ git checkout develop [user@localhost sage]$ make The second line fails because the folder is called `tracmirror` and not `sage`. When I run `make` as instructed I get the error "Sage source tree is unconfigured. Please run "./configure" first." However just after cloning there is no 'configure' file in the folder. Note that the same problem arises with instructions at https://doc.sagemath.org/html/en/developer/walk_through.html#obtaining-the-sage-source-code Also, the page https://doc.sagemath.org/html/en/installation/source.html#general-procedure instructs to run `configure` right after cloning, which fails because the file does not exits. According to the main readme ( https://github.com/sagemath/sage#instructions-to-build-from-source ) it seems that the correct way to build sage from source from scratch is to first run `make configure` (step 5). By the way steps 5 and 4 could be switched in this file, as step 4 refers to the file `configure` that does not exist before step 5. Shouldn't we keep a single page with up-to-date instructions instead of multiple duplicates that are hard to maintain? Le 08/09/2021 à 05:51, John H Palmieri a écrit : > Could you please open a ticket for this? > > On Tuesday, September 7, 2021 at 3:47:44 PM UTC-7 Nils Bruin wrote: > >> On: >> >> https://doc.sagemath.org/html/en/developer/manual_git.html >> >> it is suggested to start with >> >> git clone https://gitlab.com/sagemath/dev/tracmirror.git >> >> however, the gitlab mirror is stuck at 9.3. The github mirror tracks the >> development tree much better. Shouldn't we be pointing people to that >> instead? Or perhaps straight to trac.sagemath.org ? >> >> Incidentally, on FC 33 and FC 34, the default settings are pretty strict >> for cryptographic signatures, and "ssh g...@trac.sagemath.org info" fails >> as a result. A way of making FC >=33 more accepting of outdated signature >> schemes is by: >> >> sudo update-crypto-policies --set LEGACY >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/9c053650-d2bf-4c22-f478-2b190e3ffcc6%40uca.fr.
