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 way out is to check in configure
and fail fast.
How about poking PATH there for suspicious segments like "/opt/" and
"/usr/local/", and suggesting removal?
Cheers,
-- Thorsten
Attachment:
pgp0jp9766b_v.pgp
Description: PGP signature
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.