On Thu, Oct 03, 2013 at 10:35:54AM -0400, Daniel J. Luke wrote:
> the gcc manpage indicates that there's some extra magic ("Mark it as a
> system directory, so that it gets the same special treatment as is
> applied to the standard system directories.") that may or may not be
> what we want in this
;>> ghostscript and pianobar) do that. Which brings up the question of whether
>>> we should change MacPorts' default configure.cppflags to that. Would there
>>> be any harm?
>>
>> where is -isystem documented?
>
> I found it in the gcc document
the question of whether
>> we should change MacPorts' default configure.cppflags to that. Would there
>> be any harm?
>
> where is -isystem documented?
I found it in the gcc documentation in the same place where -I is documented:
http://gcc.gnu.org/onlinedocs/gcc/Directo
ndle that issue is to replace "`-I${prefix}/include`"
> with "`-isystem${prefix}/include`", and several ports (like freetype,
> ghostscript and pianobar) do that. Which brings up the question of whether we
> should change MacPorts' default configure.cppflags to tha
simply written
"`configure.cppflags-prepend -I.`".
But another way to handle that issue is to replace "`-I${prefix}/include`" with
"`-isystem${prefix}/include`", and several ports (like freetype, ghostscript
and pianobar) do that. Which brings up the question of whether w
