All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Select MTD before EXT2/CRAMFS/SQUASHFS are built
Date: Wed, 24 Jan 2007 23:57:53 +0100	[thread overview]
Message-ID: <20070124225753.GD28221@aon.at> (raw)
In-Reply-To: <053601c73f56$016879f0$01c4af0a@atmel.com>

On Wed, Jan 24, 2007 at 02:18:07AM +0100, Ulf Samuelsson wrote:
>Erik Andersen wrote:
>> On Tue Jan 23, 2007 at 11:34:48PM +0100, Ulf Samuelsson wrote:
>>> Building a file sysrtem will fail if the mtd tools are not
>>> available. THis patch ensure MTD is selected if either of
>>> ext2/cramfs/squashfs are selected.
>>
>> Nak.  There are a great many situations where people use ext2
>> and/or cramfs and/or squashfs without wanting to also use MTD...
>> I happen to use all of them without wanting MTD at various times.
>>
>> -Erik
>
>Hmm,
>
>The intention is, that if ext2/squashfs/cramfs etc is selected,
>you ensure you build the  MTD utilities for the *host*.

What specific failure do you see?


Since you seem to use cramfs, may i ask you to look if these patches are ok?
http://busybox.net/bugs/view.php?id=512
http://busybox.net/bugs/view.php?id=1027
>
>$ mkfs.ext2 etc.
>
>Not that you put the MTD utilities into the root file system.
>How do I do what I intended then?
>(I hope building the host tools is not inconvenient).

I do not want to download nor build a package that i do not need..

  reply	other threads:[~2007-01-24 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 22:34 [Buildroot] [PATCH] Select MTD before EXT2/CRAMFS/SQUASHFS are built Ulf Samuelsson
2007-01-24  0:07 ` Erik Andersen
2007-01-24  1:18   ` Ulf Samuelsson
2007-01-24 22:57     ` Bernhard Fischer [this message]
2007-01-24 23:51       ` [Buildroot] [PATCH] Select MTD before EXT2/CRAMFS/SQUASHFS arebuilt Ulf Samuelsson
2007-01-25  8:46         ` Bernhard Fischer

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=20070124225753.GD28221@aon.at \
    --to=rep.dot.nop@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.