From: Marco <developement333@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] bFLT build in precompiled ARM enviroment
Date: Mon, 17 Dec 2007 17:58:47 +0100 [thread overview]
Message-ID: <4766AAC7.3020806@gmx.net> (raw)
In-Reply-To: <019801c84096$388bd7a0$dcc4af0a@atmel.com>
>I am not aware that there is such a thing like a precompiled ARM
buildroot system.
hm, do i mix something here up?
http://www.uclibc.org/toolchains.html
http://www.uclibc.org/downloads/root_fs_arm.ext2.bz2
>No, the way to build any application,m is to add a directory to the
"package" directory and then >add a "<package>.mk" and a "Config.in"
file in that directory.
uhm. ok. you can point me to documentataion about that?
marco
Ulf Samuelsson schrieb:
> | hello list,
> |
> | i've an running ARM enviroment, i downloaded the precompiled ARM
> | buildroot system.
>
> I am not aware that there is such a thing like a precompiled ARM buildroot system.
>
> now i want to build a "hello worl" bFLT binary.
> | however, ive found that compiling bFLT should be something like:
> | gcc hw.c -elf2flt
>
> No, the way to build any application,m is to add
> a directory to the "package" directory and then
> add a "<package>.mk" and a "Config.in" file in that directory.
>
>
> | it spits out an error about the entry point, however compiles to the end
> | and is executeable. if i do "file" on the binary it signs it as an "ELF"
> | file. so elf2flt was not working i guess.
> | can someone tell/link me how to build bflt binaries, is it possible with
> | the precompiled enviroment anyway?
> |
> | thanx
>
> If you want to use jst the toolchain generated by buildroot for somthing
> else, then you are probably sending the mail to the wrong mailing list.
>
>
> Best Regards
> Ulf Samuelsson
>
>
next prev parent reply other threads:[~2007-12-17 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 0:52 [Buildroot] bFLT build in precompiled ARM enviroment Marco
2007-12-17 9:28 ` Ulf Samuelsson
2007-12-17 16:58 ` Marco [this message]
2007-12-17 19:04 ` 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=4766AAC7.3020806@gmx.net \
--to=developement333@gmx.net \
--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