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
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 text was updated successfully, but these errors were encountered:
The build system names the static library with a
_s
suffix, 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-lyajl
linker flag to link against it. You need to specify-lyajl_s
. Notably, thepkg-config
file that gets generated from the build does not tellpkg-config
about this. Runningpkg-config --static --libs yajl
still recommends-lyajl
as the appropriate linker flag, which causes downstream builds usingpkg-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 text was updated successfully, but these errors were encountered: