On October 12, 2025 11:15:10 PM CDT, "'[email protected]' via sage-devel" 
<[email protected]> wrote:
>Most of these targets are coming from the docbuild. 

Why would one consider docbuild targets 
for the task of building sagelib?

Shouldn't src/doc be considered separately?


> Does someone knows if 
>sphinx's incremental rebuild is now good enough that we can remove our 
>custom-made multi-stage docbuild? 

As far as I understand, the main objective of the old docbuild was to speed it 
up, compared to how sphinx was doing more than 10 years ago. I imagine it's 
good enough now, but it doesn't seem to be a trivial task to rewire our docs to 
use the standard sphinx build.

Dima
>
>On Monday, October 13, 2025 at 11:25:58 AM UTC+8 [email protected] wrote:
>
>> I do see a progress output while meson is generating build.ninja (i.e. 
>> ninja's makefile), and it took about 230 seconds of wallclock time.
>> (Often it's much faster, but major rebuilds, when you touched configure.ac 
>> and what not, are like this)
>>
>> [sagelib-10.8.beta6] [spkg-install]   Build targets in project: 1680
>> [sagelib-10.8.beta6] [spkg-install] 
>> [sagelib-10.8.beta6] [spkg-install]   SageMath 10.8.beta6
>> [sagelib-10.8.beta6] [spkg-install] 
>> [sagelib-10.8.beta6] [spkg-install]     User defined options
>> [sagelib-10.8.beta6] [spkg-install]       Native files   : 
>> /home/dima/software/sage-src/build/pkgs/../platform/meson/sage-configure-native-file.ini
>> [sagelib-10.8.beta6] [spkg-install]                       
>>  /home/dima/software/sage-src/build/sage-distro/meson-python-native-file.ini
>> [sagelib-10.8.beta6] [spkg-install]       SAGE_LOCAL     : 
>> /home/dima/software/sage-src/local
>> [sagelib-10.8.beta6] [spkg-install]       b_ndebug       : if-release
>> [sagelib-10.8.beta6] [spkg-install]       b_vscrt        : md
>> [sagelib-10.8.beta6] [spkg-install]       buildtype      : release
>> [sagelib-10.8.beta6] [spkg-install]       default_library: static
>> [sagelib-10.8.beta6] [spkg-install] 
>> [sagelib-10.8.beta6] [spkg-install]   Found ninja-1.13.1 at /usr/bin/ninja
>> [sagelib-10.8.beta6] [spkg-install] 
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:   0%|          | 
>> 0/1680 eta ?
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  11%|█▏        | 
>> 189/1680 eta 00:00
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  22%|██▎       | 
>> 378/1680 eta 00:00
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  51%|█████     | 
>> 850/1680 eta 00:00
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  84%|████████▍ | 
>> 1419/1680 eta 00:00
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  84%|████████▍ | 
>> 1419/1680 eta 00:00
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  89%|████████▉ | 
>> 1494/1680 eta 00:04
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  89%|████████▉ | 
>> 1495/1680 eta 00:04
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  89%|████████▉ | 
>> 1495/1680 eta 00:04
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  91%|█████████ | 
>> 1530/1680 eta 00:10
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  91%|█████████ | 
>> 1531/1680 eta 00:10
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  91%|█████████ | 
>> 1531/1680 eta 00:10
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  91%|█████████▏| 
>> 1537/1680 eta 00:40
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  92%|█████████▏| 
>> 1538/1680 eta 00:40
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  92%|█████████▏| 
>> 1538/1680 eta 00:40
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  92%|█████████▏| 
>> 1552/1680 eta 00:44
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  92%|█████████▏| 
>> 1553/1680 eta 00:44
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  92%|█████████▏| 
>> 1553/1680 eta 00:44
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  94%|█████████▍| 
>> 1576/1680 eta 00:50
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  94%|█████████▍| 
>> 1577/1680 eta 00:50
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  94%|█████████▍| 
>> 1577/1680 eta 00:50
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  95%|█████████▌| 
>> 1600/1680 eta 00:49
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  95%|█████████▌| 
>> 1601/1680 eta 00:49
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  95%|█████████▌| 
>> 1601/1680 eta 00:49
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  96%|█████████▌| 
>> 1616/1680 eta 02:12
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  96%|█████████▋| 
>> 1617/1680 eta 02:07
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  98%|█████████▊| 
>> 1644/1680 eta 00:39
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets:  99%|█████████▉| 
>> 1663/1680 eta 00:13
>> [sagelib-10.8.beta6] [spkg-install]   Generating targets: 100%|█████████▉| 
>> 1677/1680 eta 00:02
>> [sagelib-10.8.beta6] [spkg-install] 
>> [sagelib-10.8.beta6] [spkg-install] 
>> [sagelib-10.8.beta6] [spkg-install]   Writing build.ninja:   0%|         
>>  | 0/3487 eta ?
>>
>> That's of course a constraint satisfaction problem to find the targets to 
>> rebuild, and it's not a very easy one.
>> I actually don't know what these almost 1700 dependencies are. Are they 
>> the sage-distro dependencies, or only sagelib?
>>
>> Once build.ninja is generated, things move quite fast in general.
>>
>> Dima
>>
>> On Sunday, October 12, 2025 at 2:47:27 AM UTC-5 [email protected] wrote:
>>
>>> OK, it took about ten minutes with configure --enable-dot2tex=yes
>>>
>>> Martin
>>> On Sunday, 12 October 2025 at 09:38:43 UTC+2 Martin R wrote:
>>>
>>>> (for comparison, previously installing dot2tex took just a few seconds)
>>>>
>>>> On Sunday, 12 October 2025 at 09:36:04 UTC+2 Martin R wrote:
>>>>
>>>>> On Sunday, 12 October 2025 at 04:14:24 UTC+2 [email protected] wrote:
>>>>>
>>>>> it might take a lot of time to create the correct list of targets, as 
>>>>> you don't follow the best way, which is
>>>>>
>>>>> ./configure --enable-dot2tex=yes
>>>>> make # this should also build do2tex
>>>>>
>>>>>
>>>>> I thought that this would be the default (if installed, which it is):
>>>>>
>>>>> --enable-dot2tex={no|if_installed (default)|yes} 
>>>>>                          enable build and use of the optional package 
>>>>> dot2tex: Create PGF/TikZ 
>>>>>                          commands from Graphviz output 
>>>>>                          * package info: ./sage -info dot2tex
>>>>>
>>>>> I'll try anyway.  But in fact, that also means that I have to be more 
>>>>> careful than previously, since there are several packages I only install 
>>>>> when I notice that something isn't working (eg., dot2tex, lie, coxeter3, 
>>>>> gap_packages, fricas, bliss, macaulay2 ...)
>>>>>  
>>>>>
>>>>> On Sat, Oct 11, 2025 at 6:12 PM Volker Braun <[email protected]> 
>>>>> wrote:
>>>>>
>>>>> Does it actually hang there? the "meson setup" step takes quite a long 
>>>>> time but eventually completes for me
>>>>>
>>>>>
>>>>> More than 3 minutes?  If so, it would be nice if there could be some 
>>>>> progress output.
>>>>>
>>>>> I'll report,
>>>>>
>>>>> Martin
>>>>>
>>>>
>

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/93755ADA-9B7E-4614-BC5E-67CD322B7C47%40gmail.com.

Reply via email to