* [Buildroot] mkcramfs invalid option 'q'
@ 2012-11-30 0:50 Woody Wu
2012-11-30 7:28 ` Peter Korsgaard
0 siblings, 1 reply; 3+ messages in thread
From: Woody Wu @ 2012-11-30 0:50 UTC (permalink / raw)
To: buildroot
Hi, list
What now concerns me is an warning message in the output of building
cramfs image:
...
tdir=/home/buildroot/buildroot-2012.08/output/target
table='/home/buildroot/buildroot-2012.08/output/build/_device_table.txt'
/home/buildroot/buildroot-2012.08/output/host/usr/bin/mkcramfs: invalid
option -- 'q'
...
I just want to ensure that this is normal and I don't need to warry
about it. Otherwise, please someone tell me a fix. Thanks!
--
woody
I can't go back to yesterday - because I was a different person then.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] mkcramfs invalid option 'q'
2012-11-30 0:50 [Buildroot] mkcramfs invalid option 'q' Woody Wu
@ 2012-11-30 7:28 ` Peter Korsgaard
2012-12-01 2:14 ` Woody Wu
0 siblings, 1 reply; 3+ messages in thread
From: Peter Korsgaard @ 2012-11-30 7:28 UTC (permalink / raw)
To: buildroot
>>>>> "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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] mkcramfs invalid option 'q'
2012-11-30 7:28 ` Peter Korsgaard
@ 2012-12-01 2:14 ` Woody Wu
0 siblings, 0 replies; 3+ messages in thread
From: Woody Wu @ 2012-12-01 2:14 UTC (permalink / raw)
To: buildroot
On 2012-11-30, Peter Korsgaard
<jacmet@uclibc.org> wrote:
>>>>>> "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.
Sorry, my understanding .... does it mean this error message is harmless
and I will not show up in furture buildroot versions?
>
> Notice: I would strongly suggest you move to squashfs instead of the
> ancient cramfs.
Thanks for the suggestion, I like to switch to a mordern image format.
cramfs is just a temporary option since at this moment when I was
testing the new kernel, I have to let it work with a verified old
rootfs, which is a cramfs.
--
woody
I can't go back to yesterday - because I was a different person then.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-12-01 2:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-30 0:50 [Buildroot] mkcramfs invalid option 'q' Woody Wu
2012-11-30 7:28 ` Peter Korsgaard
2012-12-01 2:14 ` Woody Wu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox