On 13/4/20 12:45 pm, Xi Ruoyao via lfs-dev wrote: > On 2020-04-13 12:01 +1000, Christoph Willing via lfs-dev wrote: >> gnome-shell-3.36.1 from svn Version 2020-04-11 fails with: >> >> [19/187] Generating gnome-extensions.1 with a custom command. >> FAILED: subprojects/extensions-tool/man/gnome-extensions.1 >> /usr/bin/a2x -D subprojects/extensions-tool/man --xsl-file >> ../subprojects/extensions-tool/man/stylesheet.xsl -f manpage >> ../subprojects/extensions-tool/man/gnome-extensions.txt >> File "/usr/bin/a2x", line 76 >> print '%s: %s' % (PROG,msg) >> ^ >> SyntaxError: invalid syntax >> >> >> I initially worked around this by adding -Dman=false to the command line >> i.e. >> >> mkdir build && \ >> cd build && \ >> meson --prefix=/usr -Dsystemd=false -Dman=false .. && \ >> ninja >> >> That enabled the build to succeed, although without addressing the >> underlying a2x problem. >> >> Looking at the a2x problem, I believe the invalid syntax problem is >> because I have: >> /usr/bin/python -> python3 > > Don't do that. > >> If I change that to: >> /usr/bin/python -> python2 >> >> then the build succeeds (although with a warning which I don't see when >> /usr/bin/python -> python3): >> [40/187] Generating gnome-extensions.1 with a custom command. >> a2x: WARNING: --destination-dir option is only applicable to HTML based >> outputs >> >> >> I don't recall how /usr/bin/python became symlink to python3 - perhaps >> it should be to python2. Maybe that should be made explicit somewhere? > > BLFS book explicitly said asciidoc deps on Python 2. > >> >> BTW I see there is an asciidoc-py3 available at: >> https://github.com/asciidoc/asciidoc-py3 >> >> Is it worth moving to that? > > It's 9.0.0rc2. We are waiting for 9.0.0 release. I'll create a ticket to > track. >
OK, thanks. chris -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
