From: Alex Song <songqf9@yahoo.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Using external toolchain / disabling Buildroot toolchain
Date: Wed, 13 Dec 2006 14:13:45 -0500 (EST) [thread overview]
Message-ID: <287497.12093.qm@web50006.mail.yahoo.com> (raw)
In-Reply-To: <loom.20061213T195208-342@post.gmane.org>
I had this situation before since we were forced to
use glibc. I'm not sure of a better, easier or
preferred way but I modified the files and only used
buildroot to build the packages.
Regards,
Alex
--- MikeW <mw_phil@yahoo.co.uk> wrote:
> 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 ?
>
> (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
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-12-13 19:13 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 [this message]
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 ` [Buildroot] Using external toolchain / disabling Buildroottoolchain Ulf Samuelsson
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=287497.12093.qm@web50006.mail.yahoo.com \
--to=songqf9@yahoo.ca \
--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