From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] mkcramfs invalid option 'q'
Date: Thu, 29 Nov 2012 23:28:18 -0800 [thread overview]
Message-ID: <87fw3rczxp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <slrnkbg0lg.2kq.narkewoody@zuhnb712.local.com> (Woody Wu's message of "Fri, 30 Nov 2012 00:50:48 +0000 (UTC)")
>>>>> "Woody" == Woody Wu <narkewoody@gmail.com> writes:
Woody> Hi, list
Woody> What now concerns me is an warning message in the output of building
Woody> cramfs image:
Woody> ...
Woody> tdir=/home/buildroot/buildroot-2012.08/output/target
Woody> table='/home/buildroot/buildroot-2012.08/output/build/_device_table.txt'
Woody> /home/buildroot/buildroot-2012.08/output/host/usr/bin/mkcramfs: invalid
Woody> option -- 'q'
Woody> ...
Woody> I just want to ensure that this is normal and I don't need to warry
Woody> about it. Otherwise, please someone tell me a fix. Thanks!
I looked back in git history, and we have apparently had this -q option
ever since cramfs support was introduced in 2003! I've removed it now
from git as mkcramfs doesn't take a -q option, thanks.
Notice: I would strongly suggest you move to squashfs instead of the
ancient cramfs.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-11-30 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 0:50 [Buildroot] mkcramfs invalid option 'q' Woody Wu
2012-11-30 7:28 ` Peter Korsgaard [this message]
2012-12-01 2:14 ` Woody Wu
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=87fw3rczxp.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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