public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Martin Sebor <msebor@gmail.com>,
	Michael Mishourovsky <mike.mishky@samsung.com>,
	gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: compiling gcc 5.x from the scratch: issues
Date: Thu, 10 Sep 2015 19:15:00 -0000	[thread overview]
Message-ID: <20150910191551.GA421@x4> (raw)
In-Reply-To: <CAH6eHdTojLkBZdyPrK39-4_XLcwmSvx3kyBc865VdZh32JsM8w@mail.gmail.com>

On 2015.09.10 at 19:53 +0100, Jonathan Wakely wrote:
> On 10 September 2015 at 17:23, Martin Sebor wrote:
> > FWIW, I think the more common source of problems for those new
> > to building GCC is not having all the right prerequisites. The
> > GCC configure script tries to detect whether the right versions
> > are available but does only a superficial job (checks their
> > version macros) which can lead to cryptic build failures down
> > the line when not all the right architectures are installed
> > (e.g., the i686 in addition to x86_64). It also proceeds when
> > MPC is not installed at all which then causes the build to fail.
> 
> Not having the right prerequisites certainly used to be a common
> problem (not quite as common as having them but installing them
> outside ld.so's search dirs and then not setting LD_LIBRARY_PATH).
> However, since I've been on a crusade to stop people doing that by
> pointing them at https://gcc.gnu.org/wiki/InstallingGCC and telling
> them to use contrib/download_prerequisites it is *much* less common
> than it used to be.
> 
> Markus, I think your patch wouldn't hurt, and might help people who
> fail to read the instructions carefully, so I suggest sending it to
> gcc-patches for review.

I did that already and Jeff has approved the patch. Will commit it
tomorrow.

-- 
Markus

  reply	other threads:[~2015-09-10 19:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  5:36 Michael Mishourovsky
2015-09-10  6:40 ` Markus Trippelsdorf
2015-09-10  6:49   ` Markus Trippelsdorf
2015-09-10 16:23     ` Martin Sebor
2015-09-10 18:53       ` Jonathan Wakely
2015-09-10 19:15         ` Markus Trippelsdorf [this message]
2015-09-10 19:17           ` Jonathan Wakely
  -- strict thread matches above, loose matches on Subject: below --
2015-09-09  8:37 Michael Mishourovsky
2015-09-09  8:50 ` Markus Trippelsdorf
2015-09-09  9:21   ` Jonathan Wakely

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=20150910191551.GA421@x4 \
    --to=markus@trippelsdorf.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=mike.mishky@samsung.com \
    --cc=msebor@gmail.com \
    /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).