#13590: Jinja2 python2 ends in error
--------------------+------------------------
Reporter: ken@… | Owner: blfs-book
Type: defect | Status: new
Priority: normal | Milestone: 9.2
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
--------------------+------------------------
Comment (by ken@…):
To my immense surprise (given that only a Python3 module gets installed by
Jinja2), everything completed.
Looking at the logs from qtwebengine-5.15.0, no mention of Jinja, the
references to jinja seem to be all for python2 :
{{{
ken@origin ~ $grep jinja /home/logs/LFS-svn-20200526-glibcdef/desktop5
/qtwebengine-everywhere-src-5.15.0.log
[932/18172] /usr/bin/python2
../../../../src/3rdparty/chromium/third_party/inspector_protocol/code_generator.py
--jinja_dir ../../../../src/3rdparty/chromium/third_party/ --output_base
gen/components/ui_devtools --config
../../../../src/3rdparty/chromium/components/ui_devtools/inspector_protocol_config.json
--inspector_protocol_dir //third_party/inspector_protocol
[3601/18172] /usr/bin/python2
../../../../src/3rdparty/chromium/third_party/inspector_protocol/code_generator.py
--jinja_dir ../../../../src/3rdparty/chromium/third_party/ --output_base
gen/content/browser/devtools --config
../../../../src/3rdparty/chromium/content/browser/devtools/protocol_config.json
--inspector_protocol_dir //third_party/inspector_protocol --config_value
protocol.path=gen/third_party/blink/public/devtools_protocol/protocol.json
[3629/18172] /usr/bin/python2
../../../../src/3rdparty/chromium/third_party/inspector_protocol/code_generator.py
--jinja_dir ../../../../src/3rdparty/chromium/third_party/ --output_base
gen/third_party/blink/renderer/core --config
../../../../src/3rdparty/chromium/third_party/blink/renderer/core/inspector/inspector_protocol_config.json
--inspector_protocol_dir //third_party/inspector_protocol --config_value
imported.path=../../../../src/3rdparty/chromium/v8/include/js_protocol.pdl
[3692/18172] /usr/bin/python2
../../../../src/3rdparty/chromium/third_party/blink/renderer/bindings/scripts/code_generator.py
gen/third_party/blink/renderer/bindings/scripts
gen/third_party/blink/renderer/bindings/scripts/cached_jinja_templates.stamp
[3697/18172] touch
obj/third_party/blink/renderer/bindings/scripts/cached_jinja_templates.stamp
[4375/18172] /usr/bin/python2
../../../../src/3rdparty/chromium/third_party/dawn/generator/dawn_json_generator.py
--dawn-json ../../../../src/3rdparty/chromium/third_party/dawn/dawn.json
--wire-json
../../../../src/3rdparty/chromium/third_party/dawn/dawn_wire.json
--targets dawn_headers --template-dir /scratch/working/qtwebengine-
everywhere-
src-5.15.0/src/3rdparty/chromium/third_party/dawn/generator/templates
--jinja2-path /scratch/working/qtwebengine-everywhere-
src-5.15.0/src/3rdparty/chromium/third_party/jinja2 --output-json-tarball
gen/third_party/dawn/dawn_headers_gen.json_tarball --depfile
gen/third_party/dawn/dawn_headers_gen.json_tarball.d --expected-outputs-
file gen/third_party/dawn/dawn_headers_gen.expected_outputs --allowed-
output-dirs-file gen/third_party/dawn/dawn_headers_gen.allowed_output_dirs
[10011/18172] /usr/bin/python2
../../../../src/3rdparty/chromium/v8/third_party/inspector_protocol/code_generator.py
--jinja_dir ../../../../src/3rdparty/chromium/third_party/ --output_base
gen/v8/src/inspector --config
../../../../src/3rdparty/chromium/v8/src/inspector/inspector_protocol_config.json
--inspector_protocol_dir //v8//third_party/inspector_protocol
}}}
I'm expecting to do a fresh build of cross-chap5 on this system in the
next week or two, trying -O2 -march=native in glibc re my sigfpe quest.
I'll remove Jinja2 from my buildscript, and find out whether it really is
needed for qtwebengine.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/13590#comment:3>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
