From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Adding nasm to toolchain
Date: Wed, 20 Dec 2006 18:16:39 +0100 [thread overview]
Message-ID: <20061220171639.GA24825@aon.at> (raw)
In-Reply-To: <5e15b0e10612200157l48183bd9tb77fc3c56f8981e9@mail.gmail.com>
On Wed, Dec 20, 2006 at 10:57:53AM +0100, Rory Slegtenhorst wrote:
>Hi,
>
>I'm working on integrating our software package into buildroot.
>Shouldn't be all that hard, but just one tiny matter.
>A small portion of our code needs nasm to compile.
>
>How can I incorporate nasm into the toolchain without needing it on the target?
>I only need it in compile time...
look at the -host targets, e.g. mtd
HTH,
prev parent reply other threads:[~2006-12-20 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 9:57 [Buildroot] Adding nasm to toolchain Rory Slegtenhorst
2006-12-20 17:16 ` Bernhard Fischer [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=20061220171639.GA24825@aon.at \
--to=rep.nop@aon.at \
--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