On 06/11/2015 01:42 PM, David Tardon wrote:
Actually, I just found out that this can be a problem on OS X as well. A
recent build of master fails in liborcus if there is boost installed
from Homebrew. Because, unfortunately, Homebrew installs stuff into
/usr/local and the boost.m4 script used by liborcus looks there...
...which answers my question
  "And while presence of pkg-config on the PATH might be a good 
heuristic to detect that the environment has been contaminated by 
MacPorts or their like, is polluting PATH the only thing those do (and 
which we would thus need to counter), or are they also polluting in 
other ways that subtly influence the build (and then cause headaches)?"
and implies that 
<http://cgit.freedesktop.org/libreoffice/core/commit/?id=ada6281a5bd74d0ff6ae578d57f39f65b7c25103> 
"configure: make the error message for pkg-config on Mac more 
actionable" fails to take into account my assumption
  "Using presence of pkg-config as a canary to detect polluted 
environments was probably born out of pragmatism.  I guess that there 
are further problems with polluted environments beyond presence of 
pkg-config."
Context
- Re: Mac OS X and pkg-config (continued)
 
  Re: Mac OS X and pkg-config · Norbert Thiebaud
  Re: Mac OS X and pkg-config · Khaled Hosny
  Re: Mac OS X and pkg-config · Khaled Hosny
   
 
  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.