You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 31, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 31, 2025. It is now read-only.
ERROR: conanfile.py (OrbitProfiler/None): Error in build() method, line 94 (related to libQt5Core.so.5) #4329
I tried to run ./bootstrap-orbit.sh with run_tests set to False in the conanfile.py inside a container of Ubuntu 20.04 with gcc 9.4.0 and qt 5.12.8. I got error as following:
make: *** [Makefile:101: all] Error 2
ERROR: conanfile.py (OrbitProfiler/None): Error in build() method, line 94
cmake.build(target=str(self.options.build_target) if self.options.build_target else None)
ConanException: Error 2 while executing cmake --build '/software/orbit/build_default_relwithdebinfo' '--' '-j16'
When I looked some previous lines, I found that this error probably was resulted from the following error:
AutoUic subprocess error
------------------------
The uic process failed to compile
"SRC:/src/CaptureFileInfo/LoadCaptureWidget.ui"
into
"SRC:/build_default_relwithdebinfo/src/CaptureFileInfo/CaptureFileInfo_autogen/include/ui_LoadCaptureWidget.h"
included by
"SRC:/src/CaptureFileInfo/LoadCaptureWidget.cpp"
Command
-------
/usr/lib/qt5/bin/uic -o /software/orbit/build_default_relwithdebinfo/src/CaptureFileInfo/CaptureFileInfo_autogen/include/ui_LoadCaptureWidget.h /software/orbit/src/CaptureFileInfo/LoadCaptureWidget.ui
Output
------
/usr/lib/qt5/bin/uic: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
Hi, can you call the uic tool in a termal and does that work?
/usr/lib/qt5/bin/uic --version
If not that means there is something wrong with your Qt installation.
I was searching online and found that people do sudo strip --remove-section=.note.ABI-tag /usr/lib/x86_64-linux-gnu/libQt5Core.so.5. After doing this, with run_tests=False, I reached the
[100%] Built target OrbitQtTests
[100%] Built target Orbit
successfully, so that I think I built successfully. However, when I set run_tests=True. I got lots of error of Failed to attach: Operation not permitted as following. I guess those tests are not required for me to run the built binary, right? But still would be nice to have all tests pass.
Running main() from /root/software/orbit/src/Test/test_main.cpp
Note: Google Test filter = MemoryRemoteTest.read
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from MemoryRemoteTest
[ RUN ] MemoryRemoteTest.read
Failed to attach: Operation not permitted
/root/software/orbit/third_party/libunwindstack/tests/MemoryRemoteTest.cpp:53: Failure
Value of: Attach(pid)
Actual: false
Expected: true
[ FAILED ] MemoryRemoteTest.read (7 ms)
[----------] 1 test from MemoryRemoteTest (7 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (7 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] MemoryRemoteTest.read
1 FAILED TEST
Start 1255: MemoryRemoteTest.read_fail
1240/3020 Test #1253: MemoryRemoteTest.read_large .......................................................................................................................................................................................................................................................................................................................................................***Failed 0.07 sec
Running main() from /root/software/orbit/src/Test/test_main.cpp
Note: Google Test filter = MemoryRemoteTest.read_large
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from MemoryRemoteTest
[ RUN ] MemoryRemoteTest.read_large
Failed to attach: Operation not permitted
/root/software/orbit/third_party/libunwindstack/tests/MemoryRemoteTest.cpp:82: Failure
Value of: Attach(pid)
Actual: false
Expected: true
[ FAILED ] MemoryRemoteTest.read_large (14 ms)
[----------] 1 test from MemoryRemoteTest (14 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (14 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] MemoryRemoteTest.read_large
1 FAILED TEST
Activity
beckerhe commentedon Nov 2, 2022
Hi,
can you call the uic tool in a termal and does that work?
If not that means there is something wrong with your Qt installation.
mxxgkz commentedon Nov 2, 2022
I was searching online and found that people do
sudo strip --remove-section=.note.ABI-tag /usr/lib/x86_64-linux-gnu/libQt5Core.so.5. After doing this, withrun_tests=False, I reached thesuccessfully, so that I think I built successfully. However, when I set
run_tests=True. I got lots of error ofFailed to attach: Operation not permittedas following. I guess those tests are not required for me to run the built binary, right? But still would be nice to have all tests pass.At the end of stdout, I got
Any suggestion? Thanks
beckerhe commentedon Nov 3, 2022
Are you running this in an environment where the ptrace syscall is not allowed? Maybe a docker container?