Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Ney <philippe.ney@pardes.ws>
To: buildroot@busybox.net
Subject: [Buildroot] newbie comment/question
Date: Mon, 29 Jan 2007 08:47:29 +0100	[thread overview]
Message-ID: <20070129084729.53400382.philippe.ney@pardes.ws> (raw)
In-Reply-To: <45BD7FCC.7070801@critical.com>

> I downloaded BuildRoot according to the documentation, tried to jump 
> ahead but failed, then went back to the documentation and found that a 
> default build failed too.  The problem was that the latest uclibc 
> snapshot failed to build.  I got over that by falling back to the 
> uclibc.x.x.1 option instead.  (This had worked when I tried to jump 
> ahead, but my attempt to build for an i486 target then failed on some 
> sort of missing kernel patch target.)  OK, with this i686 build complete 
> (after falling back to an earlier version of uclibc), I was unable to 
> find a kernel to load onto my target.  I didn't see this problem 
> documented anywhere.  How do I compile (or cross-compile, since my goal 
> is to use BuildRoot as a cross-platform development tool if possible) a 
> kernel image under BuildRoot?  Is this outside the scope of BuildRoot?  
> I just came over from OpenEmbedded because their support for uclibc 
> seems to be deficient, and I didn't see any mention of kernel building 
> in the BuildRoot docs.  Any help would be appreciated.

Hello,

Sure you can !
In the sources, have a look in target/device
And in the configuration view go in "Board Support Options"

Philippe

  reply	other threads:[~2007-01-29  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29  5:02 [Buildroot] newbie comment/question James L Henrickson
2007-01-29  7:47 ` Philippe Ney [this message]
2007-01-29 15:12 ` [Buildroot] newbie comment/question - kernel building MikeW

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=20070129084729.53400382.philippe.ney@pardes.ws \
    --to=philippe.ney@pardes.ws \
    --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