Arch Linux User Repository

Damn, it didn't even occur to me that such a library incompatibility would error out not only during runtime but also during compilation. Shame on me. I've pushed an update with libjwt2.

It looks like zoneminder probably isn't compatible with libjwt 3.2.1:

[ 25%] Building CXX object src/CMakeFiles/zm.dir/zm_crypt.cpp.o
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp: In function ‘std::pair<std::__cxx11::basic_string<char>, unsigned int> verifyToken(std::string, std::string)’:
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:29:9: error: ‘jwt_new’ was not declared in this scope
   29 |   err = jwt_new(&jwt);
      |         ^~~~~~~
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:35:9: error: ‘jwt_set_alg’ was not declared in this scope; did you mean ‘jwt_get_alg’?
   35 |   err = jwt_set_alg(jwt, JWT_ALG_HS256, (const unsigned char*)key.c_str(), key.length());
      |         ^~~~~~~~~~~
      |         jwt_get_alg
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:37:5: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   37 |     jwt_free(jwt);
      |     ^~~~~~~~
      |     jwt_free_t
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:42:9: error: ‘jwt_decode’ was not declared in this scope
   42 |   err = jwt_decode(&jwt, jwt_token_str.c_str(),
      |         ^~~~~~~~~~
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:45:5: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   45 |     jwt_free(jwt);
      |     ^~~~~~~~
      |     jwt_free_t
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:50:24: error: ‘jwt_get_grant’ was not declared in this scope; did you mean ‘jwt_get_alg’?
   50 |   const char *c_type = jwt_get_grant(jwt, (const char*)"type");
      |                        ^~~~~~~~~~~~~
      |                        jwt_get_alg
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:52:5: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   52 |     jwt_free(jwt);
      |     ^~~~~~~~
      |     jwt_free_t
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:56:5: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   56 |     jwt_free(jwt);
      |     ^~~~~~~~
      |     jwt_free_t
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:63:5: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   63 |     jwt_free(jwt);
      |     ^~~~~~~~
      |     jwt_free_t
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:71:35: error: ‘jwt_get_grant_int’ was not declared in this scope
   71 |   token_issued_at = (unsigned int)jwt_get_grant_int(jwt, "iat");
      |                                   ^~~~~~~~~~~~~~~~~
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:73:5: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   73 |     jwt_free(jwt);
      |     ^~~~~~~~
      |     jwt_free_t
/home/gregory/aur/zoneminder/src/zoneminder-1.36.35/src/zm_crypt.cpp:79:3: error: ‘jwt_free’ was not declared in this scope; did you mean ‘jwt_free_t’?
   79 |   jwt_free(jwt);
      |   ^~~~~~~~
      |   jwt_free_t
make[2]: *** [src/CMakeFiles/zm.dir/build.make:163: src/CMakeFiles/zm.dir/zm_crypt.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:605: src/CMakeFiles/zm.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Judging by the v3.0.0 changelog/description and also by the mere fact that the version jumped from 2.x to 3.x (which usually implies backward incompatibility), I suspect that this version bump will indeed create issues with ZoneMinder.

But as I don't use this package myself I can't verify this, so I've asked upstream about it and for the time being I'll refrain from arbitrarily changing the dependency to libjwt2 until we know for sure.

Just an FYI: libjwt branch 2.x moved to aur/libjwt2 - not sure if this package works with libjwt 3.x

Alright thanks for letting me know, I shall ask the developers on upstream about it.

Thank you for you time.

@gameslayer Sorry, but I'm completely clueless when it comes to ARM stuff, and the log you've posted doesn't clearly mention a specific error. All I could find by googling is that building ZM on/for ARM is known to be a bit finicky, and as far as I can see the developers don't even provide an official ARM docker image, which I think is telling.

So your best guess is mine as well, and your best bet would probably be to try and ask support from upstream, unless somebody else here happens to know about that stuff better than me and you and is able to help you.

fails to build on Arm64

[ 16%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/net/TcpServer.cpp.o
[ 17%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/net/TcpSocket.cpp.o
[ 17%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/net/Timer.cpp.o
[ 18%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/net/Timestamp.cpp.o
[ 19%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/AACSource.cpp.o
[ 19%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/DigestAuthenticator.cpp.o
[ 20%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/G711ASource.cpp.o
[ 21%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/H264Parser.cpp.o
[ 21%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/H264Source.cpp.o
[ 22%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/H265Source.cpp.o
[ 23%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/MediaSession.cpp.o
[ 23%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/RtpConnection.cpp.o
[ 24%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/RtspConnection.cpp.o
[ 25%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/RtspMessage.cpp.o
[ 25%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/RtspPusher.cpp.o
[ 26%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/RtspServer.cpp.o
[ 27%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/xop/VP8Source.cpp.o
[ 27%] Linking CXX static library libRtspServer.a
[ 27%] Built target RtspServer
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I won't change distros to please the zoneminder development staff, let's be clear. linux is linux.

zoneminder-git is up for anyone who may want it. Of course, here be dragons and all that jazz.

Also, seeing as the 1.36.35 hotfix has been taking a while, I've just pushed an update for 1.36.34 with the FFmpeg 7.0 patch by @shella included. I don't know how well it will run, but at least now it will build.

@simona They're thinking that deploying ZM on an unsupported rolling distro is not a priority use case for them to fix potential regressions. Upstream explicitly supports only LTS distros (e.g. Redhat, Ubuntu LTS, etc) and docker containers, which would not be affected by the FFmpeg 7.0 issue (LTS distros will take years to upgrade from 6.0 or even 5.0, and containers are a controlled environment where you can ship/bundle whatever library version you require/support).

but excuse me... you keep the system constantly updated and you have to uninstall and give up the sw and it wouldn't be a priority? but how do they think?