On 28.04.2023 00:24, Nathan Sidwell wrote: > On 4/25/23 11:04, Jan Beulich wrote: >> On 28.06.2022 16:06, Jan Beulich wrote: >>> The pathname underneath gcm.cache/ is determined from the effective name >>> used for the main input file of a particular module. When modules are >>> built, no canonicalization occurs for the main input file. Hence the >>> module file wouldn't be found if a different (the canonicalized) file >>> name was used when importing that same module. (This is an effect of >>> importing happening in the preprocessor, just like #include handling.) >>> >>> Since it doesn't look easy to make module generation use libcpp's >>> maybe_shorter_path() (in fact I'd consider this a layering violation, >>> while cloning the logic would - at least in principle - be prone to both >>> going out of sync), simply suppress system header path canonicalization >>> for the respective tests. >> >> Ping: This still looks to apply as is. > > ok -- I was unaware of this. might be sensible to file a defect about this?
Sure: 109660. Jan
