wn they claim a workaround would cause that GCC
bug report is caused by having to deal with cycle detection becoming
more complicated if you cannot just remove duplicate entries from the
include path.
--
Met vriendelijke groet,
With kind regards,
Giel van Schijndel
On 04-05-18 16:30, Giel van Schijndel wrote:
> I'm currently trying to produce a minimal test case, I'll post it here
> when I succeed.
I've put the test case at https://git.fsfe.org/giel/hello-cpp17. It only
uses a simple makefile.
PS The web interface doesn't seem t
On 04-05-18 14:43, Ludovic Courtès wrote:
> Hi,
>
> Giel van Schijndel skribis:
>
>> On 09-03-18 13:42, Ludovic Courtès wrote:
>>> julien lepiller skribis:
>>>
>>>> I'm trying to build a software that requires gcc>=7.2. Unfortunately,
>
ommand and capture its output from within the build phases, let alone
parse and use its result to clean up CPLUS_INCLUDE_PATH.
--
Met vriendelijke groet,
With kind regards,
Giel van Schijndel
