On 11/17/10 21:47, Peter Rosin wrote: > If you take some random proprietary compiler on some > random proprietary unix, you expect autotools to cope.
No, actually, I don't expect that. For example, on Solaris 10, I must pass some arguments to 'configure', or otherwise I won't be using the proprietary compiler, or I'll be compiling in 32-bit mode when I obviously want 64-bit, or I'll be linking to the wrong libraries, or whatever. It's pretty common, actually, that some arguments will be required to get a proper build on Solaris. It shouldn't be surprising that arguments might be required for a Microsoft environment too. > Autoconf > adding -g -- when -g is an unknown option -- is just the kind of thing > that gives you bad vibes. Yes, but it works well in practice. It's not perfect, but it's good enough. Perhaps Autoconf-generated scripts should also add -nologo automatically, as well as -g. Would that solve the problem? It'd be a lot simpler, if it works, and it wouldn't require such an intimate connection to the way Microsoft spells their copyright notice. If done right, it wouldn't require any more processes than are already used, I'd think.