Dan Eble <[email protected]> writes: > On Jan 30, 2020, at 13:39, David Kastrup <[email protected]> wrote: >> >>> I just had a successful mage -j5 doc as of commit >>> 8a05312fd8d2a56ec724a793b313949db0cfe729 >> >> Current stable/2.20 which failed on my system. > > I also am not able to reproduce the problem in a clean workspace; but > I have verified that I want more cores. :)
Well, LilyPond builds were the reasons I invested in a 4-core processor my T420 laptop is not designed for thermally. And the doc build is the main contributor to LilyPond build time. >> Traceback (most recent call last): >> File "/usr/local/tmp/lilypond/scripts/build/out/www_post", line 101, in >> <module> >> os.symlink (p, dest) >> OSError: [Errno 2] No such file or directory >> # clear __builtin__._ >> # clear sys.path >> # clear sys.argv >> # clear sys.ps1 >> # clear sys.ps2 >> >> in the central portion. Which does not appear to help at all. Any idea >> what I could/should do to figure out where stuff goes wrong with my >> system? One thing I could do is check with current master. > > How about editing www_post to print the values of p and dest so we can > see for which file os.symlink is failing? I'll take a look. Right now I am in another doc build run, but I'll get back. -- David Kastrup
