Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using a precompiled busybox toolchain as an external toolchain
Date: Tue, 18 Dec 2012 16:32:10 +0100	[thread overview]
Message-ID: <20121218163210.1573a9c7@skate> (raw)
In-Reply-To: <CAKvQZ_3-v9ArCy0b6Q9VmzNToDaigk1=USPJsgUKpEptzeP1yA@mail.gmail.com>

Dear Willy Lambert,

On Tue, 18 Dec 2012 16:19:47 +0100, Willy Lambert wrote:

> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaah. To be honest an entry
> in the manual to state this would be nice.

Indeed. Feel free to submit a patch for the manual :-)

> thanks, should I understand that I can't publish the buildroot
> toolchain on another  PC without installing it at the __same__ place ?

Your understanding is correct. Making the toolchain relocatable is part
of our TODO-list, though.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-12-18 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 12:42 [Buildroot] Using a precompiled busybox toolchain as an external toolchain Willy Lambert
2012-12-18 12:53 ` Thomas Petazzoni
2012-12-18 15:19   ` Willy Lambert
2012-12-18 15:32     ` Thomas Petazzoni [this message]
2012-12-18 16:50       ` Willy Lambert
2012-12-30 12:56         ` Willy Lambert
2012-12-30 13:53           ` Samuel Martin
2013-01-10 23:01             ` Willy Lambert
2013-01-23  8:44             ` Willy Lambert
2013-01-29 15:57               ` Willy Lambert
2013-01-29 16:08                 ` Thomas Petazzoni
2013-01-29 16:49                   ` Willy Lambert
2013-01-29 17:01                     ` Thomas Petazzoni

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=20121218163210.1573a9c7@skate \
    --to=thomas.petazzoni@free-electrons.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