Hello! > Ian and you do agree on this point. In fact, much of this thread is > precisely on this point. Pavel says, IIUC, that it does do harm to > some people to use --target when they meant something else. I > understand now why it would be wrong to issue an error for this issue. I don't insist on warnings. As long as unknown options are ignored but not listed by "--help" it would be consistent for "--target" to behave in the same way. We yet have to solve the generic problem - how to impose strict checking for options without breaking configure in subdirectories. This is a big separate problem, so let's do it later. Pavel
- Re: Is this a bug in autoconf? (patch... Christopher Seawood
- Re: Is this a bug in autoconf? (patch... Tom Tromey
- Re: Is this a bug in autoconf? (patch... Akim Demaille
- Re: Is this a bug in autoconf? (patch... Akim Demaille
- Re: Is this a bug in autoconf? (patch... Pavel Roskin
- Re: Is this a bug in autoconf? (patch... Peter Eisentraut
- Re: Is this a bug in autoconf? (patch... Tom Tromey
- Re: Is this a bug in autoconf? (patch... Akim Demaille
- Re: Is this a bug in autoconf? (patch... Tom Tromey
- Re: Is this a bug in autoconf? (patch... Akim Demaille
- Re: Is this a bug in autoconf? (patch... Pavel Roskin
- Re: Is this a bug in autoconf? (patch... Ian Lance Taylor
- Re: Is this a bug in autoconf? (patch... Ian Lance Taylor
- Re: Is this a bug in autoconf? (patch... Peter Eisentraut
- Re: Is this a bug in autoconf? (patch... Mo DeJong
- Re: Is this a bug in autoconf? (patch... Alexandre Oliva
- Re: Is this a bug in autoconf? (patch... Ian Lance Taylor
- Re: Is this a bug in autoconf? Tom Tromey
- Re: Is this a bug in autoconf? Ian Lance Taylor