public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/34922] toplevel ./configure --help is incomplete Date: Tue, 22 Jan 2008 19:41:00 -0000 [thread overview] Message-ID: <20080122180458.7033.qmail@sourceware.org> (raw) In-Reply-To: <bug-34922-11811@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from aldot at gcc dot gnu dot org 2008-01-22 18:04 ------- You should document this (awkward) flag in the --help output, though. Still, it is inconsistent to mention just a few of the possible arguments in the help text, thus my question: Should all toplevel libdirs be listed in the help text or should none of the toplevel libdirs be listed in the help text? If the latter, then let's please add a short note to the help text that mentiones these implied arguments, e.g. --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) where PACKAGE can be any toplevel lib directory except libgcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34922
next prev parent reply other threads:[~2008-01-22 18:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-22 14:17 [Bug c/34922] New: toplevel ./configure --help aldot at gcc dot gnu dot org 2008-01-22 14:18 ` [Bug c/34922] toplevel ./configure --help is incomplete aldot at gcc dot gnu dot org 2008-01-22 17:56 ` [Bug bootstrap/34922] " Ralf dot Wildenhues at gmx dot de 2008-01-22 19:41 ` aldot at gcc dot gnu dot org [this message] 2008-01-22 19:51 ` brian at dessent dot net 2008-01-22 21:14 ` Ralf dot Wildenhues at gmx dot de 2008-01-22 22:39 ` Ralf dot Wildenhues at gmx dot de 2008-01-23 7:13 ` Ralf dot Wildenhues at gmx dot de 2008-01-30 15:55 ` bonzini at gcc dot gnu dot org 2008-01-30 17:14 ` bonzini at gnu dot org
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=20080122180458.7033.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).