johncblacker
commented
3 years ago Actuall, I ran nm -A _framework_bindings.cpython-37m-arm-linux-gnueabihf.so and the symbol is defined. I went to the same .so file from a build of mediapipe for version -0.8.4 and the same symbol that was in the error was/is in both versions of this file. So, something strange is going on. If I do an import mediapipe from python with the newer built (latest master) I get the error; if I issue import mediapipe with the older build, it works fine. Please...need some help fixing this problem.
Followed this "recipe" for building on Raspberry Pi, but I was trying on Pi 3b+ and I am using bazel from "bazel-bin" and I get the undeclared symbol error. I've tried varying some of the opencv BUILD parameters to no avail - don't think it's at all related to the third_party opencv_build; however, I haven't found a posted solution online that works to correct the issue. I was having a problem building bazel and then found the pre-built version "bazel-bin" and the build seems to complete normally, as far as I can tell. Is there a solution to this problem? I'm just guessing that it's environment related since others don't seem to have the issue at all. The symbol starts out: "_ZN3ruy28Pack8bit..." I used nm -gCD on the .so file and and the symbol string doesn't appear in the output; but I did find "0070de58 T ruy::Pack8bitColMajorForNeon2Cols(ruy::Packparams8bit const&)" for what it's worth. The bazel I'm using is 3.7.2- (@non-git) according to bazel --version.