This is a protection-from-contaminated-system
But in general, a system can be contaminamed in arbitrary ways.
Should/can we really protect against arbitrary, unknown, ways in which
a system might have been changed by helpful 3rd-party software or
misguided sysadmins/users to not correspond to a
Yes, we can't protect against an arbitrarily broken system.
I'm not a good systems administrator. I don't know how to do please
consider hiding it without breaking something else.
I think pango is faulty; it needs to depend on how cairo was
configured, but it is testing how the system is
Tor Lillqvist wrote:
What we should do, IMHO, is to check in our own configure.in if there
is a pkg-config in PATH on a system where one is not expected to be
present (only Mac OS X, I guess?), and in that case emit a warning.
But wait, we already do that!
Have to agree with Tor here, best
