rib/gputop

Compilation fails when running on Python3

Opened this issue · 1 comments

Debian testing no longer packages python2, causing the build to fail.

I hacked subprojects/wslay-d72ea2ea9e24032144ab85f840e3aaf8cd5d6e07/lib/includes/wslay/meson.build to call python3 instead, which worked around the lack of mako.template.

I also had to comment out the uvtest lines in subprojects/libuv-v1.18.0/meson.build, because it complained about multiple definitions of `sock'

@djdeath I'm not sure I can submit an MR for this because those files are being pulled from your wraps.

I encounter this issue too(intel i5-10505 ubuntu 22.04), I link /usr/bin/python3 -> python3.10

/usr/bin/ld: subprojects/libuv-v1.18.0/uvtest.p/test_test-poll-closesocket.c.o:/home/felix/github/gputop/build/../subprojects/libuv-v1.18.0/test/test-poll-closesocket.c:28: multiple definition of sock'; subprojects/libuv-v1.18.0/uvtest.p/test_test-poll-close-doesnt-corrupt-stack.c.o:/home/felix/github/gputop/build/../subprojects/libuv-v1.18.0/test/test-poll-close-doesnt-corrupt-stack.c:35: first defined here /usr/bin/ld: subprojects/libuv-v1.18.0/uvtest.p/test_test-poll-closesocket.c.o:/home/felix/github/gputop/build/../subprojects/libuv-v1.18.0/test/test-poll-closesocket.c:29: multiple definition of handle'; subprojects/libuv-v1.18.0/uvtest.p/test_test-poll-close-doesnt-corrupt-stack.c.o:/home/felix/github/gputop/build/../subprojects/libuv-v1.18.0/test/test-poll-close-doesnt-corrupt-stack.c:36: first defined here
collect2: error: ld returned 1 exit status
[612/739] Compiling C object lib/libgputop_client.a.p/meson-generated_.._gputop-gens-metrics.c.o
ninja: build stopped: subcommand failed.