From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] Using external toolchain / disabling Buildroottoolchain
Date: Fri, 26 Jan 2007 19:45:39 +0100 [thread overview]
Message-ID: <02a401c7417c$928c0af0$01c4af0a@atmel.com> (raw)
In-Reply-To: loom.20070126T192656-570@post.gmane.org
MikeW wrote:
> MikeW <mw_phil@...> writes:
>
>>
>> Buildroot cannot build a required toolchain, but I would still like
>> to use it to build everything else.
>>
>> Is there a preferred way to disable building the toolchain, and to
>> set Buildroot to use an external toolchain instead ?
It would be good to specify a toolchain once, and be done with
it, so you don't have to rebuild the toolchain
every time you start on a new version of buildroot.
>> (This is 'inside-out' from the BR docs which say how to use the BR
>> toolchain from outside.)
>>
>> Looking at the top-level Makefile, this looks as if it would involve
>> edits to the file(s).
>>
>> Regards,
>> MikeW
>>
>
> Looks like there's a possible patch here
> http://bugs.uclibc.org/view.php?id=237
>
> Don't you wish there was a 'patch gallery' ?!
>
> MikeW
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM: +46 (706) 22 44 57
Tel: +46 (8) 441 54 22
Fax: +46 (8) 441 54 29
Mail: Box 2033 174 02 Sundbyberg
Visit: Kavalleriv?gen 24
174 58 Sundbyberg'
Sweden
prev parent reply other threads:[~2007-01-26 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 18:58 [Buildroot] Using external toolchain / disabling Buildroot toolchain MikeW
2006-12-13 19:13 ` Alex Song
2006-12-13 19:28 ` Bernhard Fischer
2006-12-14 9:29 ` [Buildroot] Using external toolchain / toolchain as package MikeW
2007-01-26 18:28 ` [Buildroot] Using external toolchain / disabling Buildroot toolchain MikeW
2007-01-26 18:45 ` Ulf Samuelsson [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='02a401c7417c$928c0af0$01c4af0a@atmel.com' \
--to=ulfs@dof.se \
--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