From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: Re: Relocating a toolchain built with crosstool-ng
Date: Tue, 28 Feb 2017 18:35:00 -0000 [thread overview]
Message-ID: <b9523ac0-ffad-4da7-29f3-4f06d60843da@att.net> (raw)
In-Reply-To: <CAPv8kTFbcgpT26N+ez6UkMHb9d_5=BKNzWLO7p9=hMEfB+1bUg@mail.gmail.com>
On 02/28/2017 09:41 AM, rdbirt wrote:
> Hi,
>
> Previously I have been able to move toolchains built with crosstool-ng
> to a different directory and run the various programs from the new
> location.
>
> Now Buildroot complains that it cannot find sysroot when using a
> toolchain I have relocated. The path returned from '<prefix>-gcc
> --print-file-name=libc.a' is the original directory where the
> toolchain was built, not the directory where the toolchain currently
> resides.
I don't recall any changes to this effect in crosstool-ng. Anyway,
please file an issue on github, I'll have a look at that.
Regards,
Alexey.
prev parent reply other threads:[~2017-02-28 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 17:41 rdbirt
2017-02-28 18:35 ` Alexey Neyman [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=b9523ac0-ffad-4da7-29f3-4f06d60843da@att.net \
--to=stilor@att.net \
--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).