public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tom dot browder at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/37210] Prohibit Default Builds in the GCC Source Tree
Date: Sun, 24 Aug 2008 22:08:00 -0000	[thread overview]
Message-ID: <20080824220717.4628.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37210-15412@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from tom dot browder at gmail dot com  2008-08-24 22:07 -------
Andrew, you're right--it's not prohibited, but my argument is that it should be
prohibited as the default build (but have a specific configure variable to
allow it), at least until it is tested.  Over the years I've watched people
have a build  problem, and the first thing the gurus tell them is *don't* build
in the gcc tree, so this enhancement would at least get newbies' attention
instead of continuing to waste help bandwidth.  Note the recommendation to not
build in the tree has been around I'll guess for at least ten years.  And with
the complexity of the build I doubt that the tested in-tree build will ever be
a requirement for a release.

I envision a short but succinct message telling about the prohibition and
adding a link to more detail.  The installation instructions should perhaps
have text enhancement or other edits to highlight the reason for the
prohibition.  


-- 


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


  parent reply	other threads:[~2008-08-24 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 11:52 [Bug other/37210] New: " tom dot browder at gmail dot com
2008-08-24 21:30 ` [Bug other/37210] " pinskia at gcc dot gnu dot org
2008-08-24 22:08 ` tom dot browder at gmail dot com [this message]
2008-08-25 20:42 ` manu at gcc dot gnu dot org
2009-09-21 16:44 ` rwild at gcc dot gnu dot org
     [not found] <bug-37210-4@http.gcc.gnu.org/bugzilla/>
2010-09-26 17:48 ` rwild 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=20080824220717.4628.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).