On Sun, 2014-11-23 at 00:11 +0000, Luís Oliveira wrote:
On Sat, Nov 22, 2014 at 11:41 PM, Stelian Ionescu sionescu@cddr.org wrote:
I strongly object to this last change. When one requests the use of pkg-config, it is because code depending on it needs to access some headers in paths that pkg-config returns, and ignoring that pkg-config is not installed or returned an error will only lead to mysterious errors later, typically unknown types or macros, so please revert commit 41016200d2a8555aa3635a2738652317acdc195c
Won't it fail straight away when trying to include the header?
Most often than not, but I know of cases where the headers for the current version of a library are put directly under /usr/include, whereas the older versions are in subdirectories of /usr/include and require pkg-config, and therefore if pkg-config is not used, the CFFI code will be compiled against the wrong(newer) library. IIRC, this is the case with BerkeleyDB and Postgres's libpq on some distributions.