From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Error while installing dosfstools: mkdosfs’: No such file or directory
Date: Wed, 10 Jul 2013 14:07:37 -0300 [thread overview]
Message-ID: <51DD94D9.6060001@zacarias.com.ar> (raw)
In-Reply-To: <20130710185808.56c3ac52@skate>
On 07/10/2013 01:58 PM, Thomas Petazzoni wrote:
> Dear Daniel Hilst Selli,
>
> On Wed, 10 Jul 2013 13:40:57 +0000, Daniel Hilst Selli wrote:
>
>> Here, this solves my problem.
>> http://pastebin.com/esGFdC0n
>
> Can you send a proper patch with this fix?
How so?
There's something fishy with this "bug".
The tool renaming happened with dosfstools 3.0.18, hence 3.0.16 behaves
the exact same way as before (mkdosfs instead of mkfs.fat and so on).
Either the 3.0.16 tarball he has isn't really 3.0.16 or i don't know
what's up.
Daniel: did you try removing the source tarball and trying a new download?
Regards.
next prev parent reply other threads:[~2013-07-10 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 20:08 [Buildroot] Error while installing dosfstools: mkdosfs’: No such file or directory Daniel.
2013-07-08 20:29 ` Peter Korsgaard
[not found] ` <CAF3SDA7tGGeJfP2kJcf9Hy6Z4KrqUhHV0E1JBTE+0x+-bCMEMw@mail.gmail.com>
2013-07-09 5:23 ` Peter Korsgaard
2013-07-10 8:41 ` Daniel Hilst Selli
2013-07-10 10:36 ` Daniel Hilst Selli
2013-07-10 10:44 ` Daniel Hilst Selli
2013-07-10 13:40 ` Daniel Hilst Selli
2013-07-10 16:58 ` Thomas Petazzoni
2013-07-10 17:07 ` Gustavo Zacarias [this message]
2013-07-10 17:29 ` Magnus Edenhill
2013-07-10 17:55 ` Peter Korsgaard
[not found] ` <alpine.LSU.2.10.1307111112110.7453@schiller.dip.t-dialin.net>
2013-07-11 14:28 ` Gustavo Zacarias
2013-07-12 20:22 ` Peter Korsgaard
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=51DD94D9.6060001@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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