public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/40516] --without-mpc, --without-ppl, --without-cloog does the same thing. No turning off mpc via configure.
Date: Wed, 22 Jul 2009 05:19:00 -0000	[thread overview]
Message-ID: <20090722051932.26797.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40516-17864@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from manu at gcc dot gnu dot org  2009-07-22 05:19 -------
(In reply to comment #4)
> How come this is still sitting unconfirmed? This is something that involves
> Linux et. al. Using --without-cloog, ppl, or mpc doesn't work right as per
> previous post, so it is more than just cosmetic. 

Presumably, because GCC devs haven't had time to look at this in detail and it
is not a priority compared to other issues. Note that at this moment there are
1288 unconfirmed bugs.

> I don't really care personally, just trying to help gcc.

Thanks, any help is greatly appreciated.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40516


  parent reply	other threads:[~2009-07-22  5:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22  2:04 [Bug regression/40516] New: using --with-cloog and --with-ppl without specifying a location with = causes configuration errors xenofears at gmail dot com
2009-06-25 13:59 ` [Bug regression/40516] " nightstrike at gmail dot com
2009-06-25 20:45 ` xenofears at gmail dot com
2009-06-30  7:39 ` [Bug bootstrap/40516] --without-mpc, --without-ppl, --without-cloog does the same thing. No turning off mpc via configure xenofears at gmail dot com
2009-07-22  4:57 ` xenofears at gmail dot com
2009-07-22  5:19 ` manu at gcc dot gnu dot org [this message]
     [not found] <bug-40516-4@http.gcc.gnu.org/bugzilla/>
2021-05-31  3:56 ` pinskia at gcc dot gnu.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=20090722051932.26797.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: 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).