Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Relocate uClibc toolchain question
Date: Tue, 11 Sep 2012 10:29:42 +0000 (UTC)	[thread overview]
Message-ID: <k2n3qm$q27$1@ger.gmane.org> (raw)
In-Reply-To: CAJbs9BEw+45qVbj_zcy_iFj3dGbHdN772upUXFg=pDiaR7WEsw@mail.gmail.com

On 2012-09-10, Rishi <rishid+mailman@gmail.com> wrote:
> Hello,
>
> I have built a uClibc toolchain using Buildroot 2012.05.
> - uClibc 0.9.33
> - gcc 4.6.x
> - C++ support
>
> The toolchain works perfectly but I want to move it from my home
> directory to a directory that can be shared with the team, like
> /opt/arm_uClibc/..

In that case, it might be easier to use Crosstool-NG to build a
toolchain.  AFAICT, the toolchains it generates can be moved anywhere
(even to different machines).  [Though I think you do need the
sysroot option when you run a relocated ctng toolchain.]

-- 
Grant

      parent reply	other threads:[~2012-09-11 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 18:21 [Buildroot] Relocate uClibc toolchain question Rishi
2012-09-10 20:14 ` Samuel Martin
2012-09-10 20:31   ` Yann E. MORIN
2012-09-11 10:29 ` Grant Edwards [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='k2n3qm$q27$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox