From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Edwards To: Daniel Egger Cc: Daniel Jacobowitz , GCC Mailinglist , gcc-patches@gcc.gnu.org Subject: Re: Building with --enable-languages problematic Date: Tue, 09 Oct 2001 13:27:00 -0000 Message-id: <20011009162834.A23280@disaster.jaj.com> References: <1002646791.5644.5.camel@sonja> <20011009153007.A1495@nevyn.them.org> <1002650809.19331.4.camel@sonja> X-SW-Source: 2001-10/msg00616.html On Tue, Oct 09, 2001 at 08:06:38PM +0200, Daniel Egger wrote: > Am Die, 2001-10-09 um 21.30 schrieb 1002655807: > > > Try --enable-languages="c,c++"; > > Will do, thanks. Though I remember that the config.status failed > sometimes even without my intervention with exactly the same problem, so > maybe a fix would be wise nevertheless. Something like the completely untested patch, appended? > > I think that's how it's documented to work. > > DOH, indeed. Though mentioning that in install.texi is a bit late > for someone bootstrapping the first compiler... *cough* online web docs *cough* :-) Index: configure.in =================================================================== RCS file: /home/pme/Repositories/GCC/gcc/configure.in,v retrieving revision 1.110 diff -u -3 -p -r1.110 configure.in --- configure.in 27 Sep 2001 18:01:15 -0000 1.110 +++ configure.in 9 Oct 2001 20:25:12 -0000 @@ -1037,6 +1037,15 @@ else if test x"${enable_languages}" = x; then echo configure.in: --enable-languages needs at least one argument 1>&2 exit 1 + else + case "${enable_languages}" in + # embedded tab -- do not untabify + "*[ ]*") echo configure.in: --enable-languages arguments are not whitespace-separated 1>&2 + exit 1 + ;; + *) + ;; + esac fi fi