public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: joris <joriswu@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Install GCC guide
Date: Sat, 13 May 2017 00:01:00 -0000	[thread overview]
Message-ID: <944a3973-27fc-e926-b862-4035298a1f40@gmail.com> (raw)
In-Reply-To: <CAH6eHdT81UzZocCFa_XvS-uK1XZd8jSr0u9XM2S0Bn+eiFcDZQ@mail.gmail.com>

Hi,

I redid the build without touching binutils ( is installed on the 
system), then it works OK. The issue is when you follow the install 
guide's suggestion to unpack binutils within the source tree.

So indeed the issue is with the doc.

Once you start moving dirs from binutils to gcc tree and configure, 
things go wrong, and keep going wrong if you try to undo.

Building binutils on its own, separately works ok as well.

Joris

On 13/05/17 00:05, Jonathan Wakely wrote:
> On 12 May 2017 at 14:03, joris wrote:
>> Hi,
>>
>> The installing GCC guide contains a paragraph that says 'If you also intend
>> to build binutils (either to upgrade an existing installation or for use in
>> place of the corresponding tools of your OS), unpack the binutils
>> distribution either in the same directory or a separate one.'
>>
>> Bu according to bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80719,
>> unpacking a binutils source release within a GCC source release may not be a
>> good idea.
>>
>> Problem with building GCC is that if you do not, you end up with a missing
>> libiberty.
> I can't parse this sentence. If you do not what? Build binutils at the
> same time?
>
> It's certainly not true that you get a missing libiberty if you don't
> build binutils at the same time.

      parent reply	other threads:[~2017-05-13  0:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 13:03 joris
2017-05-12 14:05 ` Jonathan Wakely
2017-05-12 14:41   ` Jonathan Wakely
2017-05-13  0:01   ` joris [this message]

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=944a3973-27fc-e926-b862-4035298a1f40@gmail.com \
    --to=joriswu@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@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).