Fix for issue #3334: build not finding YAJL

[RooHTaylor]

When searching for YAJL during ./configure, pkg-config is checked first, and then a list of directories is searched if pkg-config bears no fruit. The previous version of yajl.m4 was looping over YAJL_POSSIBLE_LIB_NAMES instead of YAJL_POSSIBLE_PATHS and passing the lib name to the CHECK_FOR_YAJL_AT() function instead of the path. The would lead to YAJL never being found if pkg-config could not find it.

what

• if pkg-config cannot locate libyajl it will not be located via path search, as the loop is passing lib names as path instead of possible paths.
• change fixes loop definition to loop over paths instead of lib names.

why

• so that libyajl may still be located if pkg-config fails

references

#3334

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[airween]

LGTM - thanks, @RooHTaylor!