Nobody is asking shell access to build farms.
What I’m asking is for an example minimum setup, what is it that the compiler sees, and how are things setup to even trigger this problem.
You can create a github repo, you can describe it in an email.
What exactly happens to cause the same file to be seen twice with different paths. And is this setup reasonable enough that it can not be considered user error.

It’s completely unreasonable to shoot down a proposal citing a problem that can not be demonstrated. How do I know its even real?


From: Jonathan Wakely <cxx_at_[hidden]>
Sent: Monday, September 2, 2024 2:30 PM
To: std-proposals_at_[hidden]
Cc: Ville Voutilainen <ville.voutilainen_at_[hidden]>; Tiago Freire <tmiguelf_at_[hidden]>; Tom Honermann <tom_at_[hidden]>
Subject: Re: [std-proposals] Revising #pragma once



On Mon, 2 Sept 2024 at 13:25, Tiago Freire via Std-Proposals <std-proposals_at_[hidden]<mailto:std-proposals_at_[hidden]>> wrote:
I have given you a detailed explanation of the minimum set of complexity that is required of a project to even hit such a problem.
And have showed you how that minimum set must include doing things that are considered bad practice.

All I got from you is just some handwave "I have this secret setup that doesn't work but I'm not going to actually show you".
Either show us the problem or bugger off.

Please remain professional. It's not practical to use email to show a large scale build system using networked filesystems. The cases have been described fairly well, are you demanding shell access to build farms? That isn't a reasonable demand.