From: Thomas Preston <thomas.preston@codethink.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Where the cross-compiler gets shared stuff
Date: Fri, 22 Nov 2019 09:37:12 +0000 [thread overview]
Message-ID: <e077e558-7f14-5101-b566-bebf8cd6cd0c@codethink.co.uk> (raw)
In-Reply-To: <XnsAB0F51847D9ABfgotham@195.159.176.226>
On 22/11/2019 08:00, Frederick Gotham wrote:
> So how are cross-compilers supposed to work? If they are installed properly,
> do you need to give them the "--sysroot" parameter?
Check out toolchain/toolchain-wrapper.c, which hardcodes a number of toolchain
arguments (including --sysroot). Cross compiler binaries are accessed via
symlinks in $(HOST_DIR)/bin, some of which go through toolchain-wrapper.
$ ls -l output/host/bin/sparc-linux-*
lrwxrwxrwx 1 tpreston tpreston 46 Nov 21 11:18 output/host/bin/sparc-linux-addr2line -> ../opt/ext-toolchain/bin/sparc-linux-addr2line
lrwxrwxrwx 1 tpreston tpreston 39 Nov 21 11:18 output/host/bin/sparc-linux-ar -> ../opt/ext-toolchain/bin/sparc-linux-ar
lrwxrwxrwx 1 tpreston tpreston 39 Nov 21 11:18 output/host/bin/sparc-linux-as -> ../opt/ext-toolchain/bin/sparc-linux-as
lrwxrwxrwx 1 tpreston tpreston 17 Nov 21 11:18 output/host/bin/sparc-linux-c++ -> toolchain-wrapper
lrwxrwxrwx 1 tpreston tpreston 48 Nov 21 11:18 output/host/bin/sparc-linux-c++.br_real -> ../opt/ext-toolchain/bin/sparc-linux-c++.br_real
lrwxrwxrwx 1 tpreston tpreston 17 Nov 21 11:18 output/host/bin/sparc-linux-cc -> toolchain-wrapper
prev parent reply other threads:[~2019-11-22 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:00 [Buildroot] Where the cross-compiler gets shared stuff Frederick Gotham
2019-11-22 9:37 ` Thomas Preston [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=e077e558-7f14-5101-b566-bebf8cd6cd0c@codethink.co.uk \
--to=thomas.preston@codethink.co.uk \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.