MythreyaK wrote: > some of the headers in the resource directory want to be able to > #include_next standard C headers, so the resource dir has to come before the > c library's dirs
Ah I see, I wasn't aware. Is there documentation on what the right order is, or how the search works? It will help me better understand this process and how the various headers interact with each other, and why the order (before this PR) was slightly different across triples. > Given there are other platforms which are working with the original order, I > would suggest changing it back, but I'm not fully an expert on the expected > order. I am not an expert either, so happy to change it back! Do I change it back now, or do I wait for a review? > Please wait for a review Of course! I can't request reviews so thank you for adding them! This PR was mostly fell out of me experimenting with "how to get clang to support multiple triples with varying c headers under one sysroot". https://github.com/llvm/llvm-project/pull/183453 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
