Closed udit01 closed 1 month ago
:octocat: cibot: Thank you for posting issue #2602. The person in charge will reply soon.
The log messages from your Ubuntu 22.04 machine is alarming:
C compiler for the host machine: cc (gcc 11.4.0 "cc (Ubuntu 11.4.0-2ubuntu1~18.04) 11.4.0")
C linker for the host machine: cc ld.bfd 2.38
C++ compiler for the host machine: c++ (gcc 11.4.0 "c++ (Ubuntu 11.4.0-2ubuntu1~18.04) 11.4.0")
You shouldn't see packages with "18.04" in your "22.04" machine.
Try things in a clean Ubuntu 22.04 machine (e.g., from a clean docker image).
Because the status of your machine is not stable or consistent, I recommend to try it in a clean docker or try to build it with pdebuild. Please refer to the build and test state (and the yaml scripts) of github-action; they are running and testing flawlessly in a clean Ubuntu 22.04/20.04 machines.
Thank you so much. For this system, I upgraded from Ubuntu 18 to Ubuntu 22 using ubuntu's in-build upgrade manager. I guess it messed with the package versioning as you said. I tried it on a new Ubuntu 20 machine, and it installs!
I have tried to install nntrainer by 3 methods.
PPA
I followed the steps in the guide . All the dependencies and nntrainer were installed. But then when I try to build & test the resnet18 example, it shows
nnstreamer-test-dev
not installed, even though I installed that one by PPA too. The complete error log is given in the issue: #2600meson-build
Then I tried installing from source using
meson build
exactly as written in the guide, it builds but then when I run$ ninja -C build install
it failed in several gmock cases, with an error log which I have attached below. To mitigate any other problems I re-installed gmock and gtest from source as given in this answer: https://stackoverflow.com/questions/36086037/cant-build-c-c-program-with-gmock-gmock-h-too-many-errors-are-generatedusing the official google-test repository.
Even after re-installing google-test and all other libraries, it still shows the errors.
Linux self hosted build using debian/ubuntu tools
Same steps as above were performed, but ultimately when ninja was run, a similar error log was generated.
Please let me know how can it be run.
Error log for procedure 2:
Error log for procedure 3 build step: