Re: Dropping recommendation to install system headers / command line tools

2017-07-05 Thread Michael
On 2017-07-05, at 6:16 AM, Jan Stary wrote: > On Jul 05 08:38:16, a...@alum.wpi.edu wrote: > https://trac.macports.org/wiki/FAQ#defaultprefix > https://trac.macports.org/wiki/FAQ#usrlocal > > Can I install software in /usr/local while using MacPorts? > No. ... > >

Re: Dropping recommendation to install system headers / command line tools

2017-07-05 Thread Jan Stary
On Jul 05 08:38:16, a...@alum.wpi.edu wrote: > On Wed, Jul 5, 2017 at 7:14 AM, Jan Stary wrote: > >> as it avoids /usr/local/{include,lib} contamination. What are the > >> thoughts on this? > > > > What contamination? I don't even have /usr/local/ > > You may not have

Re: Dropping recommendation to install system headers / command line tools

2017-07-05 Thread Jan Stary
On Jul 03 21:21:36, jerem...@macports.org wrote: > base currently outputs a warning if system headers are not installed. I > modified the warning a few months ago when I improved our support for > building against SDKs, and it now reads: > >Warning: System headers do not appear to be

Re: Dropping recommendation to install system headers / command line tools

2017-07-04 Thread Jan Stary
On Jul 04 03:10:38, ryandes...@macports.org wrote: > Last I checked, graphite2 would not build if CLTools were not installed: > https://trac.macports.org/ticket/49325 On a related note: a comment in this ticket says that xcode-select -p does not show whether you have the command

Re: Dropping recommendation to install system headers / command line tools

2017-07-04 Thread Jeremy Huddleston Sequoia
> On Jul 4, 2017, at 01:10, Ryan Schmidt wrote: > > > On Jul 3, 2017, at 23:21, Jeremy Huddleston Sequoia wrote: > >> base currently outputs a warning if system headers are not installed. I >> modified the warning a few months ago when I improved our support for >>