This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch, toplevel] --enable-multilib*S* is an easy typo to recognize...


On Sun, Feb 15, 2004 at 02:37:36AM -0300, Alexandre Oliva wrote:
> Consider that we drop into the top level a new package that takes
> --enable-multilibs as an argument?

Ew.  I would hope we would point to gcc's spelling and say, conform or die.
:-)  If the new package needs different functionality, then they can use
a spelling that's more significantly different.


> --enable/with arguments that a package doesn't understand are supposed
> to be ignored.

And I've always appreciated that feature.  It's allowed libstdc++ to add
its own --enable's that would otherwise have been blocked.  This case
is different, but that is only an opinion and I realize may not be a
popular one.


> Patch hesitantly approved after the error is turned into a warning,
> and a sleep is added if you like.

That'd be fine with me too.  All I really want is to avoid wasting hours
tracking down innocent and common typos.  DJ suggested bailing out, so
I'll wait to hear his opinion, and anybody else who wants to jump in.


-- 
Problems are experience waiting to be acquired.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]