From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot failing when jffs2 output selected
Date: Wed, 30 Jul 2008 17:16:00 -0700 [thread overview]
Message-ID: <1217463360.6526.13.camel@kokopelli> (raw)
In-Reply-To: <1217457837.6526.6.camel@kokopelli>
On Wed, 2008-07-30 at 15:43 -0700, Brian Beattie wrote:
> I'm trying the build a jffs2 filesystem but buildroot fails when trying
> the build the host utilities with a missing include file "acl.h"
I've been looking at the mtd-utils and it looks like
for .../buildroot/toolchain_build_arm/mtd_orig, not all the patches are
getting applied. Maybe somebody who understands patch-kernel.sh better
than I could comment?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
Brian Beattie LFS12947 | "Honor isn't about making the right choices.
beattie at beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net | -- Midori Koto
next prev parent reply other threads:[~2008-07-31 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 22:43 [Buildroot] buildroot failing when jffs2 output selected Brian Beattie
2008-07-31 0:16 ` Brian Beattie [this message]
2008-07-31 7:13 ` Hinko Kocevar
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=1217463360.6526.13.camel@kokopelli \
--to=beattie@beattie-home.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