public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: "R. Diez" <rdiezmail-gcc@yahoo.de>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Specifying where Binutils is and what it is called
Date: Mon, 20 Apr 2020 11:55:32 -0700	[thread overview]
Message-ID: <CAFyWVabQ9O86=BbW=1LmFSOB9O6=fdTHcBoUSqheQ=ue+VYtxQ@mail.gmail.com> (raw)
In-Reply-To: <921250919.1086849.1587309283539@mail.yahoo.com>

On Sun, Apr 19, 2020 at 8:14 AM R. Diez via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
> The steps would look like this:
> - Build and install Binutils with --prefix=/final/destination
> - Build and install GCC phase 1 (minimal compiler) with --prefix=/temporary/destination
> - Build and install Newlib with GCC phase 1 with --prefix=/final/destination
> - Build and install GCC phase 2 with --prefix=/final/destination
> - At this point, we could delete /temporary/destination

It looks like the simple solution is to just build and install
binutils twice.  Once into temporary destination and once into final
destination.  Then each compiler will be able to find binutils.  If
you want to optimize this, you might be able to build binutils once,
and install it twice, overriding prefix at install time to put it in
the other install dir.

Jim

  parent reply	other threads:[~2020-04-20 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <921250919.1086849.1587309283539.ref@mail.yahoo.com>
2020-04-19 15:14 ` R. Diez
2020-04-19 18:49   ` Jonathan Wakely
2020-04-20  5:25     ` Kai Ruottu
2020-04-20  5:32       ` Kai Ruottu
2020-04-20 18:55   ` Jim Wilson [this message]
     [not found] <590749852.1515706.1587371249089.ref@mail.yahoo.com>
2020-04-20  8:27 ` R. Diez
2020-04-20  8:47   ` Jonathan Wakely
     [not found] <2007965762.1537196.1587376378163.ref@mail.yahoo.com>
2020-04-20  9:52 ` R. Diez
     [not found] <238241866.1719021.1587558240444.ref@mail.yahoo.com>
2020-04-22 12:24 ` R. Diez
2020-04-23  8:24   ` Christer Solskogen

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='CAFyWVabQ9O86=BbW=1LmFSOB9O6=fdTHcBoUSqheQ=ue+VYtxQ@mail.gmail.com' \
    --to=jimw@sifive.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=rdiezmail-gcc@yahoo.de \
    /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).