From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Egger <degger@fhm.edu>
Cc: GCC Mailinglist <gcc@gcc.gnu.org>
Subject: Re: Building with --enable-languages problematic
Date: Tue, 09 Oct 2001 12:30:00 -0000 [thread overview]
Message-ID: <20011009153007.A1495@nevyn.them.org> (raw)
In-Reply-To: <1002646791.5644.5.camel@sonja>
On Tue, Oct 09, 2001 at 06:59:35PM +0200, Daniel Egger wrote:
> Hija,
>
> 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
> config.status.
>
> 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
work.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-10-09 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 12:24 Daniel Egger
2001-10-09 12:29 ` guerby
2001-10-09 12:30 ` Daniel Jacobowitz [this message]
2001-10-09 13:06 ` Daniel Egger
2001-10-09 13:25 ` Gerald Pfeifer
2001-10-11 7:38 ` Daniel Egger
2001-10-12 13:56 ` Gerald Pfeifer
2001-10-09 13:27 ` Phil Edwards
2001-10-13 10:36 ` Daniel Egger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011009153007.A1495@nevyn.them.org \
--to=drow@mvista.com \
--cc=degger@fhm.edu \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).