From: "R. Diez" <rdiezmail-gcc@yahoo.de>
To: "jimw@sifive.com" <jimw@sifive.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Specifying where Binutils is and what it is called
Date: Wed, 22 Apr 2020 12:24:00 +0000 (UTC) [thread overview]
Message-ID: <238241866.1719021.1587558240444@mail.yahoo.com> (raw)
In-Reply-To: <238241866.1719021.1587558240444.ref@mail.yahoo.com>
> 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.
Finally good advice! Thanks!
That has worked. In case anybody is interested, the result is here:
https://github.com/rdiez/JtagDue/blob/master/Toolchain/Makefile
Search for INSTALL_GCC_PHASE_1_TO_SEPARATE_DIR in there for more information.
Best regards,
rdiez
next parent reply other threads:[~2020-04-22 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <238241866.1719021.1587558240444.ref@mail.yahoo.com>
2020-04-22 12:24 ` R. Diez [this message]
2020-04-23 8:24 ` Christer Solskogen
[not found] <2007965762.1537196.1587376378163.ref@mail.yahoo.com>
2020-04-20 9:52 ` R. Diez
[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] <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
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=238241866.1719021.1587558240444@mail.yahoo.com \
--to=rdiezmail-gcc@yahoo.de \
--cc=gcc-help@gcc.gnu.org \
--cc=jimw@sifive.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).