On 7/5/06, <b class="gmail_sendername">Rob Landley</b> <<a href="mailto:rob@landley.net">rob@landley.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 05 July 2006 10:37 am, Jason Schoon wrote:<br>> On 7/5/06, Mike Frysinger <<a href="mailto:vapier@gentoo.org">vapier@gentoo.org</a>> wrote:<br>> > On Wednesday 05 July 2006 00:51, Jason Schoon wrote:
<br>> > > He is building in bFLT format (uClinux binary flat format) rather than<br>> > > ELF. Seems like a worthwhile and hopefully not insurmountable task.<br>> ><br>> > it's already integrated into the build system, Shaun just wants to let
<br>> > the user add it to the default build list<br>> > -mike<br>><br>> Seems (to me) like we should do something similar to the Linux kernel.<br>> They still have those options to choose whether you want support for
<br>> a.out, ELF, etc.<br><br>That's what executable formats they support, not what kernel type is<br>generated. Specifying the kernel type you want is done via the make command<br>line. (You always get an elf kernel, vmlinux in the top level directory, and
<br>some systems actually boot that directly. The others are generated from<br>vmlinux.)<br></blockquote></div><br>True, in that case it is specifying a feature, rather than a build configuration. As Shaun pointed out, this probably belongs on the command line along with specifying cross-compiler and such.
<br><br>