From: Andreas Schwab <schwab@linux-m68k.org>
To: "Andrew Dean via gcc" <gcc@gcc.gnu.org>
Cc: Jeff Law <law@redhat.com>,
Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Andrew Dean <Andrew.Dean@microsoft.com>
Subject: Re: [EXTERNAL] Re: How to test aarch64 when building a cross-compiler?
Date: Wed, 27 Nov 2019 20:42:00 -0000 [thread overview]
Message-ID: <87d0dduk3j.fsf@igel.home> (raw)
In-Reply-To: <CY1PR00MB0121B787A81C285278F20B4BEA440@CY1PR00MB0121.namprd00.prod.outlook.com> (Andrew Dean via gcc's message of "Wed, 27 Nov 2019 20:21:41 +0000")
On Nov 27 2019, Andrew Dean via gcc wrote:
> 2. export LD_LIBRARY_PATH=${BuildRoot}/install/glibcs/aarch64-linux-gnu/lib64:${BuildRoot}/install/compilers/aarch64-linux-gnu/aarch64-glibc-linux-gnu/lib64
> 3. sudo ln -s ${BuildRoot}/install/glibcs/aarch64-linux-gnu/lib/ld-linux-aarch64.so.1 /lib/ld-linux-aarch64.so.1
Just set QEMU_LD_PREFIX to your sysroot.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2019-11-27 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 19:17 Andrew Dean via gcc
2019-11-25 20:16 ` Christophe Lyon
2019-11-25 20:28 ` [EXTERNAL] " Andrew Dean via gcc
2019-11-25 20:40 ` Adhemerval Zanella
2019-11-25 20:44 ` Ramana Radhakrishnan
2019-11-25 21:43 ` Andrew Dean via gcc
2019-11-25 21:55 ` Ramana Radhakrishnan
2019-11-26 20:53 ` Jeff Law
2019-11-27 20:21 ` Andrew Dean via gcc
2019-11-27 20:42 ` Andreas Schwab [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=87d0dduk3j.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Andrew.Dean@microsoft.com \
--cc=adhemerval.zanella@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=ramana.gcc@googlemail.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).