From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 29 Jan 2013 18:01:44 +0100 Subject: [Buildroot] Using a precompiled busybox toolchain as an external toolchain In-Reply-To: References: <20121218135336.2e24d6bc@skate> <20121218163210.1573a9c7@skate> <20130129170842.7508fa3f@skate> Message-ID: <20130129180144.6dd8a5ff@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Willy Lambert, On Tue, 29 Jan 2013 17:49:14 +0100, Willy Lambert wrote: > Yes, it's kind of you to have written all those historical details. > May I update the documentation with some of those clarifications ? Actually, most of this is already in the documentation (but not the HTML version visible on Buildroot website, since the HTML version visible is the one generated from the latest stable release, and those changes have been done after the last stable release). But if you feel something is missing, then yes, don't hesitate to submit a documentation patch! > So in the end, if I want to use the generated toolchain (in > $(O)/host) to build my own application (which is not a package, it's > the user end application) it is never relocable if I use buildroot > internal or crosstool-ng. I don't mind with that, it's just a matter > of knowing what's happening. As of today, yes, you're correct. It's however considered a bug to be fixed, though. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com