dgibson
commented
1 year ago I've hit a bunch of problems with setuptools stuff as well. Unfortunately, I don't really know enough about how it works to debug and fix it.
Open kloczek opened 1 year ago
dgibson
commented
1 year ago I've hit a bunch of problems with setuptools stuff as well. Unfortunately, I don't really know enough about how it works to debug and fix it.
kloczek
commented
1 year ago Please play with those two commands which I gave you. I'm using them to build all my +1.1k rpm packages with pyton modules.
You need to install in buiuld env modules: wheel, builder, setuptools and installer (meson provides routine in its python module to check python modules dependencies).
dgibson
commented
1 year ago I barely have time to keep up with the most minimal maintenance of dtc. I'm afraid "playing with" some commands to figure out what's going on just isn't going to happen. If you want this fixed, you're going to need to give me some muc more specific information about what needs to change here.
kloczek
commented
10 months ago FYI: I found workaround by build dtc with disabled python support and than build python module using pep517 build procedure however I've hit issue with test suite which fails in two units.
May I ask to have look on above output? 🤔
dgibson
commented
10 months ago On Sun, Oct 29, 2023 at 06:17:59PM -0700, Tomasz Kłoczko wrote:
FYI: I found workaround by build dtc with disabled python support and than build python module using pep517 build procedure however I've hit issue with test suite which fails in two units.
```console + /usr/bin/meson test -C x86_64-redhat-linux-gnu --num-processes 48 --print-errorlogs ninja: Entering directory `/home/tkloczko/rpmbuild/BUILD/dtc-1.7.0/x86_64-redhat-linux-gnu' ninja: no work to do. 1/1 run-test FAIL 6.10s exit status 1 >>> NO_PYTHON=1 MALLOC_PERTURB_=53 /home/tkloczko/rpmbuild/BUILD/dtc-1.7.0/tests/run_tests.sh ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― Listing only the last 100 lines from a long log. dtbs_equal_ordered -n test_tree1.dtb test_tree1_wrong5.test.dtb: PASS dtbs_equal_ordered -n test_tree1.dtb test_tree1_wrong6.test.dtb: PASS dtbs_equal_ordered -n test_tree1.dtb test_tree1_wrong7.test.dtb: PASS dtbs_equal_ordered -n test_tree1.dtb test_tree1_wrong8.test.dtb: PASS dtbs_equal_ordered -n test_tree1.dtb test_tree1_wrong9.test.dtb: PASS dtbs_equal_unordered test_tree1.dtb test_tree1.dtb: PASS dtbs_equal_unordered test_tree1.dtb test_tree1.dtb.reversed.test.dtb: PASS dtbs_equal_unordered test_tree1.dtb.reversed.test.dtb test_tree1.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong1.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong2.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong3.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong4.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong5.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong6.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong7.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong8.test.dtb: PASS dtbs_equal_unordered -n test_tree1.dtb test_tree1_wrong9.test.dtb: PASS dtc -I dtb -O dtb -s -o test_tree1.dtb.sorted.test.dtb test_tree1.dtb: PASS dtbs_equal_unordered test_tree1.dtb test_tree1.dtb.sorted.test.dtb: PASS dtc -I dtb -O dtb -s -o test_tree1.dtb.reversed.sorted.test.dtb test_tree1.dtb.reversed.test.dtb: PASS dtbs_equal_unordered test_tree1.dtb.reversed.test.dtb test_tree1.dtb.reversed.sorted.test.dtb: PASS dtbs_equal_ordered test_tree1.dtb.sorted.test.dtb test_tree1.dtb.reversed.sorted.test.dtb: PASS dtc -O dtb -o label01.dts.fdtget.test.dtb /home/tkloczko/rpmbuild/BUILD/dtc-1.7.0/tests/label01.dts: PASS fdtget-runtest.sh "MyBoardName" label01.dts.fdtget.test.dtb / model: PASS fdtget-runtest.sh "MyBoardName MyBoardFamilyName" label01.dts.fdtget.test.dtb / compatible: PASS fdtget-runtest.sh "77 121 66 111 97 114 100 78 97 109 101 0 77 121 66 111 97 114 100 70 97 109 105 108 121 78 97 109 101 0" -t bu label01.dts.fdtget.test.dtb / compatible: PASS fdtget-runtest.sh "MyBoardName MyBoardFamilyName" -t s label01.dts.fdtget.test.dtb / compatible: PASS fdtget-runtest.sh "32768" label01.dts.fdtget.test.dtb ***@***.*** d-cache-size: PASS fdtget-runtest.sh "8000" -tx label01.dts.fdtget.test.dtb ***@***.*** d-cache-size: PASS fdtget-runtest.sh "61 62 63 0" -tbx label01.dts.fdtget.test.dtb /randomnode tricky1: PASS fdtget-runtest.sh "a b c d de ea ad be ef" -tbx label01.dts.fdtget.test.dtb /randomnode blob: PASS fdtget-runtest.sh "MyBoardName\0MyBoardFamilyName\0" -tr label01.dts.fdtget.test.dtb / compatible: PASS fdtget-runtest.sh "\012\013\014\015\336\352\255\276\357" -tr label01.dts.fdtget.test.dtb /randomnode blob: PASS ../fdtget -tlx label01.dts.fdtget.test.dtb /randomnode mixed {!= 0}: PASS fdtget-runtest.sh "6162 6300 1234 0 a 0 b 0 c" -thx label01.dts.fdtget.test.dtb /randomnode mixed: PASS fdtget-runtest.sh "61 62 63 0 12 34 0 0 0 a 0 0 0 b 0 0 0 c" -thhx label01.dts.fdtget.test.dtb /randomnode mixed: PASS ../fdtget -ts label01.dts.fdtget.test.dtb /randomnode doctor-who {!= 0}: PASS fdtget-runtest.sh "MyBoardName\nmemory" -ts label01.dts.fdtget.test.dtb / model /memory device_type: PASS ../fdtget -tx label01.dts.fdtget.test.dtb /randomnode doctor-who {!= 0}: PASS fdtget-runtest.sh "" -tx -d label01.dts.fdtget.test.dtb /randomnode doctor-who: PASS fdtget-runtest.sh " May I ask to have look on above output? 🤔
Unfortunately, while it's showing the overall failure, I'm not seeing any of the individual failing cases. So there's really no information for me to go on here.
-- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT the other | way around! http://www.ozlabs.org/~dgibson
kloczek
commented
10 months ago Unfortunately, while it's showing the overall failure, I'm not seeing any of the individual failing cases. So there's really no information for me to go on here.
Any hint what I can try to do to diagnose this issue? 🤔
dgibson
commented
10 months ago Hmm. Does the failure also occur if you build with make instead of meson?
hybotics
commented
8 months ago I am also having problems relating to the setuptools version on my system. I run Ubuntu MATE' 22.04 on a Ryzen 9 laptop.
hybotics@shuttle
~/Repos/Github/dgibson/dtc
$ make
DEP tests/dumptrees.c
DEP tests/trees.S
DEP tests/testutils.c
DEP tests/value-labels.c
DEP tests/asm_tree_dump.c
DEP tests/truncated_memrsv.c
DEP tests/truncated_string.c
DEP tests/truncated_property.c
DEP tests/fs_tree1.c
DEP tests/check_full.c
DEP tests/check_header.c
DEP tests/check_path.c
DEP tests/overlay_bad_fixup.c
DEP tests/overlay.c
DEP tests/subnode_iterate.c
DEP tests/property_iterate.c
DEP tests/integer-expressions.c
DEP tests/utilfdt_test.c
DEP tests/path_offset_aliases.c
DEP tests/add_subnode_with_nops.c
DEP tests/dtbs_equal_unordered.c
DEP tests/dtb_reverse.c
DEP tests/dtbs_equal_ordered.c
DEP tests/extra-terminating-null.c
DEP tests/relref_merge.c
DEP tests/incbin.c
DEP tests/boot-cpuid.c
DEP tests/phandle_format.c
DEP tests/path-references.c
DEP tests/references.c
DEP tests/string_escapes.c
DEP tests/propname_escapes.c
DEP tests/appendprop2.c
DEP tests/appendprop1.c
DEP tests/del_node.c
DEP tests/del_property.c
DEP tests/setprop.c
DEP tests/set_name.c
DEP tests/rw_oom.c
DEP tests/rw_tree1.c
DEP tests/open_pack.c
DEP tests/nopulate.c
DEP tests/mangle-layout.c
DEP tests/move_and_save.c
DEP tests/sw_states.c
DEP tests/sw_tree1.c
DEP tests/nop_node.c
DEP tests/nop_property.c
DEP tests/setprop_inplace.c
DEP tests/stringlist.c
DEP tests/appendprop_addrrange.c
DEP tests/addr_size_cells2.c
DEP tests/addr_size_cells.c
DEP tests/notfound.c
DEP tests/sized_cells.c
DEP tests/char_literal.c
DEP tests/get_next_tag_invalid_prop_len.c
DEP tests/get_alias.c
DEP tests/node_offset_by_compatible.c
DEP tests/node_check_compatible.c
DEP tests/node_offset_by_phandle.c
DEP tests/node_offset_by_prop_value.c
DEP tests/parent_offset.c
DEP tests/supernode_atdepth_offset.c
DEP tests/get_path.c
DEP tests/get_phandle.c
DEP tests/get_prop_offset.c
DEP tests/getprop.c
DEP tests/get_name.c
DEP tests/path_offset.c
DEP tests/subnode_offset.c
DEP tests/find_property.c
DEP tests/root_node.c
DEP tests/get_mem_rsv.c
DEP libfdt/fdt_check.c
DEP libfdt/fdt_overlay.c
DEP libfdt/fdt_addresses.c
DEP libfdt/fdt_empty_tree.c
DEP libfdt/fdt_strerror.c
DEP libfdt/fdt_rw.c
DEP libfdt/fdt_sw.c
DEP libfdt/fdt_wip.c
DEP libfdt/fdt_ro.c
DEP libfdt/fdt.c
DEP util.c
DEP fdtoverlay.c
DEP fdtput.c
DEP fdtget.c
DEP fdtdump.c
LEX convert-dtsv0-lexer.lex.c
DEP convert-dtsv0-lexer.lex.c
DEP srcpos.c
BISON dtc-parser.tab.c
DEP dtc-parser.tab.c
LEX dtc-lexer.lex.c
DEP dtc-lexer.lex.c
DEP treesource.c
DEP livetree.c
DEP fstree.c
DEP flattree.c
DEP dtc.c
DEP data.c
DEP checks.c
CHK version_gen.h
UPD version_gen.h
DEP util.c
CHK version_gen.h
CC srcpos.o
CC util.o
CC convert-dtsv0-lexer.lex.o
LD convert-dtsv0
CC dtc.o
CC checks.o
CC data.o
CC flattree.o
CC fstree.o
CC livetree.o
CC treesource.o
CC dtc-lexer.lex.o
CC dtc-parser.tab.o
LD dtc
CC fdtdump.o
LD fdtdump
CC fdtget.o
CC libfdt/fdt.o
CC libfdt/fdt_ro.o
CC libfdt/fdt_wip.o
CC libfdt/fdt_sw.o
CC libfdt/fdt_rw.o
CC libfdt/fdt_strerror.o
CC libfdt/fdt_empty_tree.o
CC libfdt/fdt_addresses.o
CC libfdt/fdt_overlay.o
CC libfdt/fdt_check.o
LD libfdt/libfdt.so.1.7.0
LD fdtget
CC fdtput.o
LD fdtput
CC fdtoverlay.o
LD fdtoverlay
AR libfdt/libfdt.a
make[1]: Entering directory '/home/hybotics/Repos/Github/dgibson/dtc'
CHK version_gen.h
PYMOD pylibfdt/_libfdt.so
/home/hybotics/VirtualEnv/zephyr/lib/python3.10/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
warnings.warn(
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
/home/hybotics/Repos/Github/dgibson/dtc/.eggs/setuptools_scm-8.0.4-py3.10.egg/setuptools_scm/_integration/setuptools.py:30: RuntimeWarning:
ERROR: setuptools==59.6.0 is used in combination with setuptools_scm>=8.x
Your build configuration is incomplete and previously worked by accident!
setuptools_scm requires setuptools>=61
Suggested workaround if applicable:
- migrating from the deprecated setup_requires mechanism to pep517/518
and using a pyproject.toml to declare build dependencies
which are reliably pre-installed before running the build tools
warnings.warn(
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section'
make[1]: Leaving directory '/home/hybotics/Repos/Github/dgibson/dtc'```Gentle ping .. any update? 🤔
dgibson
commented
7 months ago @kloczek sorry, no progress. This is deep into the details of how setuptoools / distutils etc. work. I'm not familiar with it and I don't really have time to learn. @sjg20 any chance you can tackle this?
setuptools67.6.1.meson and meson build output:
And install fails with
Typical pep517 build and istall procedure without pip consit from:
python -sBm build -w --no-isolationthis will generate .wh in dist/ subdirectorypython -sBm installer dist/*.whl --destdir $(DESTDIR)