public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Ralf dot Wildenhues at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/34922] toplevel ./configure --help is incomplete Date: Wed, 23 Jan 2008 07:13:00 -0000 [thread overview] Message-ID: <20080123064252.17156.qmail@sourceware.org> (raw) In-Reply-To: <bug-34922-11811@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from Ralf dot Wildenhues at gmx dot de 2008-01-23 06:42 ------- (In reply to comment #5) > > > In an ideal world the toplevel configure would check at runtime and see what > > subdirs are present and adjust its output accordingly. Also --help=recursive > > should be fixed, as there are tons and tons of options that are only shown if > > you run configure --help in the subdirs, but are never shown by the toplevel > > --help. Patch posted: <http://gcc.gnu.org/ml/gcc-patches/2008-01/msg01061.html> > I guess without more intrusive hacking that will have to wait until GCC > uses Autoconf 2.62 (I just found one more glitch in there) Autoconf glitch fixed: <http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=0fd647c6364a383b13af31b45e07679c293ff09f> -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34922
next prev parent reply other threads:[~2008-01-23 6:43 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 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 [this message] 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=20080123064252.17156.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).