The build system names the static library with a _s suffix, as libyajl_s.a. This causes problems like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877285 downstream because you can't use the expected -lyajl linker flag to link against it. You need to specify -lyajl_s. Notably, the pkg-config file that gets generated from the build does not tell pkg-config about this. Running pkg-config --static --libs yajl still recommends -lyajl as the appropriate linker flag, which causes downstream builds using pkg-config to find the static library to fail.
The build system should call the static library libyajl.a on Linux, as static and dynamic libraries on Linux are supposed to have the same name.
The build system names the static library with a
_ssuffix, aslibyajl_s.a. This causes problems like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877285 downstream because you can't use the expected-lyajllinker flag to link against it. You need to specify-lyajl_s. Notably, thepkg-configfile that gets generated from the build does not tellpkg-configabout this. Runningpkg-config --static --libs yajlstill recommends-lyajlas the appropriate linker flag, which causes downstream builds usingpkg-configto find the static library to fail.The build system should call the static library
libyajl.aon Linux, as static and dynamic libraries on Linux are supposed to have the same name.