[MacPorts] #55577: getting rid of unforeseen -I${prefix}/include option adding and its potential side-effects

[MacPorts]

#55577: getting rid of unforeseen -I${prefix}/include option adding and its
potential side-effects
--------------------------+-----------------
  Reporter:  RJVB         |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  pcre, glib2  |
--------------------------+-----------------

Comment (by RJVB):

 > unless we change the pcre port in the way that you've requested.

 Suggested would be a better term :)

 > All the compilers we use support `-isystem`. gcc-4.0 didn't support it
 properly, but we don't use that anymore.

 I meant differences in how the arguments to the option are used, more
 specifically the exact resulting order of the search path. I'm not saying
 there are any just that there might be.

 > The build dependencies will be installed by the time the configure phase
 starts. They might not be there in earlier phases, nor at the time the
 portfile is parsed.

 Yes, that much was clear. Somehow I'd expect that "base" would re-parse a
 portfile after installing any missing dependencies, i.e. that there would
 be no difference between a (hypothetical)

 {{{
 > port build-dep foo
 > port configure foo
 > port build foo
 }}}

 and a direct `port build foo`, regardless of what the Portfile does (or
 almost).

--
Ticket URL: <https://trac.macports.org/ticket/55577#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS