From: Ondrej Jakubcik <ojakubcik@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Bootstrapping GCC 5.1.0 together with Binutils 2.25
Date: Wed, 01 Jul 2015 05:10:00 -0000 [thread overview]
Message-ID: <CALzwOp_zffT2sqN3SwFdVDJLD0R+PUwtBSrxP5QdhAeRg=-L7Q@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTK0fpUcLvMgx=8NUZdYY5-2UVrfOGOtJ8MdGArYwiOHA@mail.gmail.com>
Ok, that's what I'll do then. I am fine if it is expected behaviour,
but in that case it would be best to remove the combined tree
suggestion from official documentation:
https://gcc.gnu.org/install/download.html
Would it work if I checked out the appropriate tags from SVN or is
something being modified at the time of release that prevents using
the combined tree approach?
Thanks a lot,
Ondrej
On Wed, Jul 1, 2015 at 3:12 AM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 30 June 2015 at 21:50, Ondrej Jakubcik wrote:
>> Hi all,
>>
>> I am having problems with boostrapping GCC 5.1.0 using a merged tree
>> together with Binutils 2.25 and other dependencies (GMP, MPC, MPFR,
>> ISL).
>>
>> I even raised a bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66356
>
> IIRC combined-tree builds do not work for released versions of GCC and
> binutils, you need to use the latest HEAD or trunk of both for that to
> work.
>
> Why not just install binutils first, then install GCC to the same prefix?
next prev parent reply other threads:[~2015-07-01 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 20:50 Ondrej Jakubcik
2015-07-01 1:12 ` Jonathan Wakely
2015-07-01 5:10 ` Ondrej Jakubcik [this message]
2015-07-01 5:28 ` NightStrike
2015-07-01 10:07 ` 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='CALzwOp_zffT2sqN3SwFdVDJLD0R+PUwtBSrxP5QdhAeRg=-L7Q@mail.gmail.com' \
--to=ojakubcik@gmail.com \
--cc=gcc-help@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).