Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James L Henrickson <jim.henrickson@critical.com>
To: buildroot@busybox.net
Subject: [Buildroot] newbie comment/question
Date: Mon, 29 Jan 2007 00:02:04 -0500	[thread overview]
Message-ID: <45BD7FCC.7070801@critical.com> (raw)

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.

Jim

             reply	other threads:[~2007-01-29  5:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29  5:02 James L Henrickson [this message]
2007-01-29  7:47 ` [Buildroot] newbie comment/question Philippe Ney
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=45BD7FCC.7070801@critical.com \
    --to=jim.henrickson@critical.com \
    --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