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
Hi,
libosmium seems to required a newer libprotozero as there is in Debian/Stretch. So cloning protozero to the directory solved the issue. But only half way. If libprotozero-dev from Stretch is installed it gets priority over the locally cloned and the build fails (Or the required version).
It seems the included cmake/FindProtozero.cmake is not capable of searching all possible locations to satisfy the required version. It prefers /usr/include/protozero over ../protozero/ although /usr/include does not satisfy the REQUIRED version.
Flo
The text was updated successfully, but these errors were encountered:
@flohoff I recommend using backports for stretch which will give you current protozero and libosmium.
Searching ../protozero is an ugly hack, not something the CMake config should do anyway. I should probably get rid of it. @daniel-j-h has the correct solution. Maybe there is a better way, but I don't know what it is.
Hi,
libosmium seems to required a newer libprotozero as there is in Debian/Stretch. So cloning protozero to the directory solved the issue. But only half way. If libprotozero-dev from Stretch is installed it gets priority over the locally cloned and the build fails (Or the required version).
It seems the included cmake/FindProtozero.cmake is not capable of searching all possible locations to satisfy the required version. It prefers /usr/include/protozero over ../protozero/ although /usr/include does not satisfy the REQUIRED version.
Flo
The text was updated successfully, but these errors were encountered: