From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Filipp Andjelo <Filipp.Andjelo@tomtom.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Relocatable toolchain
Date: Mon, 17 Jun 2013 14:53:00 -0000 [thread overview]
Message-ID: <20130617165320.14d11ab7@skate> (raw)
In-Reply-To: <51BF2043.20605@tomtom.com>
Dear Filipp Andjelo,
On Mon, 17 Jun 2013 14:40:32 +0000, Filipp Andjelo wrote:
> I built a toolchain using crosstool-ng and it works fine, as far as I
> don't move it to another folder. I want to have a toolchain, which I can
> put everywhere, but how?
> If I run "gcc --print-sysroot", I get absolute path to the directory,
> where toolchain was built. If I check the same for google's Android
> toolchain, I get relative path
> to the gcc. How did they do that?
>
> Currently, I have a workaround using CFLAGS="--sysroot=path/to/sysroot",
> but It's not acceptable solution here.
Did you do some special configuration to Crosstool-NG? Because by
default, Crosstool-NG puts the toolchain sysroot is a correct location
that allows the toolchain to be relocatable. And it works well for me.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-06-17 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:40 Filipp Andjelo
2013-06-17 14:53 ` Thomas Petazzoni [this message]
2013-06-17 18:15 ` Filipp Andjelo
2013-06-17 18:27 ` Carsten Schoenert
2013-06-17 21:02 ` Filipp Andjelo
2013-06-17 22:36 ` Yann E. MORIN
2013-06-19 8:14 ` Filipp Andjelo
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=20130617165320.14d11ab7@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=Filipp.Andjelo@tomtom.com \
--cc=crossgcc@sourceware.org \
/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).