public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aaronwl@rm-f.net
To: gcc-gnats@gcc.gnu.org
Subject: other/5567: <manual should clarify --enable-languages>
Date: Fri, 01 Feb 2002 03:06:00 -0000	[thread overview]
Message-ID: <20020201105833.9E493FF30@SirDrinkalot> (raw)


>Number:         5567
>Category:       other
>Synopsis:       <manual should clarify --enable-languages>
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 01 03:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Aaron W. LaFramboise
>Release:        3.0.3
>Organization:
<>
>Environment:
System: Linux aaronwl 2.2.20 #1 Tue Nov 20 03:52:27 PST 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.0.3/configure --prefix=/usr/home/aaronwl/sub --program-suffix=-3.0.3 --enable-threads=posix --enable-version-specific-runtime-libs --enable-languages=c,c++ --disable-nls --with-system-zlib
>Description:
	Docs do not specify , as delimiter for --enable-languages.  This
	caused me significant grief.  There was also no error emitted
	for using an apparently invalid string ('c c++')
>How-To-Repeat:

>Fix:
	Say , is the delimiter in the docs.  Perhaps also generate an error
	for incorrect language strs.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-02-01 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  3:06 aaronwl [this message]
2002-02-01 14:46 Phil Edwards
2002-02-18 17:20 rodrigc

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=20020201105833.9E493FF30@SirDrinkalot \
    --to=aaronwl@rm-f.net \
    --cc=gcc-gnats@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).