This is the mail archive of the
mailing list for the GCC project.
Re: Building with --enable-languages problematic
- To: Daniel Egger <degger at fhm dot edu>
- Subject: Re: Building with --enable-languages problematic
- From: Daniel Jacobowitz <drow at mvista dot com>
- Date: Tue, 9 Oct 2001 15:30:07 -0400
- Cc: GCC Mailinglist <gcc at gcc dot gnu dot org>
- References: <1002646791.5644.5.camel@sonja>
On Tue, Oct 09, 2001 at 06:59:35PM +0200, Daniel Egger wrote:
> the configure script has a bug that makes it troublesome to build
> a version of gcc with only selected languages.
> Using ../gcc/configure --enable-languages="c c++" works fine on
> the first time but the build fails terribly on consecutive tries
> when the dependencies trigger a rebuild of the scripts by issueing
> The problem is that the configure call in there uses --enable-languages
> without glueing the additional arguments together by ""'s.
> Thus it looks like this
> ../gcc/configure --with-gcc-version-trigger=/devel/gcc/gcc/version.c
> --enable-languages=c c++
> and fails.
> Can anyone with more insight handle this please?
Try --enable-languages="c,c++"; I think that's how it's documented to
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer