On Sun, Jun 26, 2011 at 07:28, Joseph S. Myers <jos...@codesourcery.com> wrote: > It seems to me that what's really wanted here is to change the add_sysroot > flag for the C++ path (all of the C++ paths?), rather than adding special > code to detect paths starting with the sysroot and reinterpret them.
I considered doing that, I wasn't sure what (if any) implications that would have on the way gcc normally builds + configures / how it works when other people use flags like --with-gxx-include-dir. I couldn't think of *harm*, but it seemed to me that my change was least likely to cause harm to existing working paths. (That doesn't mean that it's the right change, just the one that I thought I could understand best. 8-) > And > so making configure detect when the --with-gxx-include-dir setting starts > with the sysroot and adjusting the flag accordingly in that case would be > a cleaner solution - that way it would be obvious that the semantics of > the relocation are exactly the same as for other sysrooted paths, whereas > it isn't when the relocation goes through different code paths in the > compiler. yeah, i can do that. thanks for the quick look. chris
