From: Phil Edwards <pedwards@disaster.jaj.com>
To: Daniel Egger <degger@fhm.edu>
Cc: Daniel Jacobowitz <drow@mvista.com>,
GCC Mailinglist <gcc@gcc.gnu.org>,
gcc-patches@gcc.gnu.org
Subject: Re: Building with --enable-languages problematic
Date: Tue, 09 Oct 2001 13:27:00 -0000 [thread overview]
Message-ID: <20011009162834.A23280@disaster.jaj.com> (raw)
In-Reply-To: <1002650809.19331.4.camel@sonja>
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
next prev parent reply other threads:[~2001-10-09 13:27 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
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 [this message]
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=20011009162834.A23280@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=degger@fhm.edu \
--cc=drow@mvista.com \
--cc=gcc-patches@gcc.gnu.org \
--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).