current state
During the development of widevine in cobalt, I put the libwidevine_cdm_shared.so file into cobalt and the following problem occurred.
libprotobuf FATAL ../../third_party/protobuf/src/google/protobuf/stubs/common.cc:89] This program was compiled against versionterminate called after throwing an instance of 'google::protobuf::FatalException'
what(): This program was compiled against version 2.5.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.0.0). Contact the program author for an update. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in "/home1/green/lekail/Widevine/SDK_Source/out/amlogic/Debug/obj/gen/protoc_out/device_files.pb.cc".)
What is the problem?
(cobalt version - RC9 ,Widevine CE CDM version- 3.0)
The error message has all the details.
Please compile libwidevine_cdm_shared.so against protobuf 3.0.0. If you didn't compile it by yourself, ask the author of libwidevine_cdm_shared.so to compile it against protobuf 3.0.0.
Related
Recently, I have installed glibc-2.35 version on my Linux distribution, before I have glibc-2.27 version. After Installing I am not able to use latest version glibc as a default for compiling source code.
As a sample trail, I have successfully compiled sample program with the latest version glibc by using following command.
gcc sample.c -o out -Wl,--rpath=/usr/lib -Wl,--dynamic-linker=/usr/lib/ld-linux-riscv64-lp64d.so.1
Here, I am facing a big difficulty is how to set latest glibc as a default glibc so that I can compile source packages normally like .configure and make -j8 and make install.
Please help me to solve this issue. I am not aware of pathcelf stuff how to use exactly.
I am testing a Linux-PAM installation with this test program. When the pam_ldap.so module is called, the test program application fails with a segmentation error. Looking at the /var/log/messages, I can red the following error message:
petalinux authpriv.err pam_test: PAM unable to dlopen(/usr/lib/security/pam_ldap.so): /lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libldap-2.4.so.2)
petalinux authpriv.err pam_test: PAM adding faulty module: /usr/lib/security/pam_ldap.so
The system is an embedded Linux running on a Zynq processor.
Can anyone help me understand the source of the problem?
Thank you.
Can anyone help me understand the source of the problem?
You linked libldap-2.4.so.2 against GLIBC-2.28 (or later).
But at runtime, the version of GLIBC is 2.27 (or earlier).
GLIBC supports backward compatibility (binaries built against earlier version of GLIBC continue to run on systems with newer GLIBC versions).
But it doesn't support "build on newer, run on older" compatibility.
I am trying this on Windows: https://github.com/cfenollosa/os-tutorial/tree/master/01-bootsector-barebones
E:\Code\MyOS\os>D:\qemu\qemu-system-x86_64.exe boot_sect_simple.bin
WARNING: Image format was not specified for 'boot_sect_simple.bin' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
Unexpected error in aio_context_set_poll_params() at /home/stefan/src/qemu/repo.or.cz/qemu/ar7/util/aio-win32.c:413:
D:\qemu\qemu-system-x86_64.exe: AioContext polling is not implemented on Windows
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
This also gives the same error:
D:\qemu\qemu-system-x86_64.exe -drive format=raw,file=boot_sect_simple.bin
QEMU version:
E:\Code\MyOS\os>D:\qemu\qemu-system-x86_64.exe -version
QEMU emulator version 2.11.90 (v2.12.0-rc0-11704-g30195e9d53-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
NASM version:
E:\Code\MyOS\os>E:\Code\MyOS\nasm-2.13.03\nasm.exe -version
NASM version 2.13.03 compiled on Feb 7 2018
This is a bug in the (release-candidate rc0) version of QEMU you are using: https://bugs.launchpad.net/qemu/+bug/1761027
It was fixed in the final 2.12.0 release. So you should upgrade your QEMU (either to 2.12.0 or to the more recent 3.0).
In general it's a bad idea to run with release-candidate versions unless you're using them specifically to test them before a full release.
I am trying to compile my own opencv 3.0.0 from source for Python 2.7.11. I find this messages. These messages appear in CMAKE.
Could NOT find PythonInterp: Found unsuitable version "2.7.11", but required is at least "3.4" (found C:/Python27/python.exe)
Could NOT find PythonInterp: Found unsuitable version "2.7.11", but required is at least "3.2" (found C:/Python27/python.exe)
And after I made the compile the first time I didn't find the Python directory that should include cv2.pyd.
Also I get this error messsage when I check the opencv_dnn_BUILD_TORCH_IMPORTER.
CMake Error at C:/opencv3/sources/opencv_contrib/modules/dnn/CMakeLists.txt:57 (message):
OPENCV_TEST_DATA_PATH environment variable was not specified
Can I find any source that has the steps of compiling opencv for Python 2.7.x on a Windows machine
By trying to install OpenCV from source on a Windows machine you are taking on a very large task. I would strongly recommend installing from the prebuilt packages available from OpenCV's website - and I'm also recommend going straight for OpenCV 3.1 rather than 3.0. You can get that install file here: http://sourceforge.net/projects/opencvlibrary/files/opencv-win/3.1.0/opencv-3.1.0.exe/download
With that said, if you still want to install from source you can get all the instructions to do this in Windows here: http://docs.opencv.org/3.0-beta/doc/tutorials/introduction/windows_install/windows_install.html
Good luck, and happy coding!
I try to compile Bluez 5.33, but after a try to configure the package, the error message configure: error: GLib >= 2.28 is required appears.
But the problem is, i am not allowed to update or install anything on this machine. How can i compile BlueZ 5.33 without updating GLib?
It depends on a newer version of GLib for a reason, it won't compile with an older version. You either build against a newer version of GLib or you stay with an older version of BlueZ.
ps: By the way, if you can't install anything on the machine, why could you use a newer version of BlueZ?