On 28 Jul 2005, Joe Buck announced authoritatively: > Glad you found this. Your experience is why I've always objected when > someone suggests a .gccrc or a GCC_OPTIONS environment variable or the > like; people will forget that they have such files and report > unreproducible bugs.
Instead, people can wrap GCC in shell scripts, use site-config files, use automated build infrastructures... we already *have* ways to do this, some with all the downsides of a .gccrc: the only advantage is that things like specs files are ill-documented, so people don't mess with them unless they know what they're doing. Fundamentally, what we want is `gcc -v' output :) don't the bug reporting guidelines already ask for this? -- `Tor employs several thousand editors who they keep in dank subterranean editing facilities not unlike Moria' -- James Nicoll
