-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/3/10 04:27 , Scott Haneda wrote: > How would files in /usr/local interfere with MacPorts as long as they are not > executable files? And wouldn't /usr/local also further have to be in your > PATH? A .h file, I can't see how that would have any impact on MacPorts > while it is building something, as MacPorts tried pretty hard to work in > prefix. I would like to understand this better, but the ticket ( > https://trac.macports.org/ticket/12336 ) did not really help me get anywhere.
configure scripts have an annoying habit of looking for libraries and include files under /usr/local no matter what you tell them to do. Additionally, if /usr/local/bin is in $PATH and any *-config scripts are installed there, configure will ask them for path information. (That has largely been superseded by pkg-config, but then you have configure adding /usr/local to the search path for *that*.) - -- brandon s. allbery [linux,solaris,freebsd,perl] [email protected] system administrator [openafs,heimdal,too many hats] [email protected] electrical and computer engineering, carnegie mellon university KF8NH -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyBPXMACgkQIn7hlCsL25UfqwCgti/6bP3Yw60HB8xUWRYdFVox g3wAnA5p3IzsLZ/vQMBeCYXtH2XjDxrg =H/wb -----END PGP SIGNATURE----- _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
