[SOLVED] NetworkManager won't compile with latest slackware64-current
by chrisVV from LinuxQuestions.org on (#588SX)
slackware64-current will not currently compile NetworkManager for me. If I run NetworkManager.Slackbuild, it fails when generating clients/common/settings-docs.h with:
Code:Traceback (most recent call last):
File "./tools/generate-docs-nm-settings-docs-merge.py", line 127, in <module>
xml_roots = list([ET.parse(f).getroot() for f in gl_input_files])
File "./tools/generate-docs-nm-settings-docs-merge.py", line 127, in <listcomp>
xml_roots = list([ET.parse(f).getroot() for f in gl_input_files])
File "/usr/lib64/python3.8/xml/etree/ElementTree.py", line 1202, in parse
tree.parse(source, parser)
File "/usr/lib64/python3.8/xml/etree/ElementTree.py", line 595, in parse
self._root = parser._parse_whole(source)
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 6, column 266
make[2]: *** [Makefile:20125: man/nm-settings-docs-dbus.xml] Error 1This doesn't matter at the moment because the supplied NetworkManager binary works fine, but it is likely to be a problem on the next upgrade. Presumably some XML parsing stuff has changed since August 20, although I cannot see anything relevant in the ChangeLog.
Code:Traceback (most recent call last):
File "./tools/generate-docs-nm-settings-docs-merge.py", line 127, in <module>
xml_roots = list([ET.parse(f).getroot() for f in gl_input_files])
File "./tools/generate-docs-nm-settings-docs-merge.py", line 127, in <listcomp>
xml_roots = list([ET.parse(f).getroot() for f in gl_input_files])
File "/usr/lib64/python3.8/xml/etree/ElementTree.py", line 1202, in parse
tree.parse(source, parser)
File "/usr/lib64/python3.8/xml/etree/ElementTree.py", line 595, in parse
self._root = parser._parse_whole(source)
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 6, column 266
make[2]: *** [Makefile:20125: man/nm-settings-docs-dbus.xml] Error 1This doesn't matter at the moment because the supplied NetworkManager binary works fine, but it is likely to be a problem on the next upgrade. Presumably some XML parsing stuff has changed since August 20, although I cannot see anything relevant in the ChangeLog.