All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Login exited
Date: Fri, 5 Sep 2008 23:09:18 +1000	[thread overview]
Message-ID: <20080905130918.GB31755@cloud.net.au> (raw)
In-Reply-To: <ed4892840809050038j3d0be1edjca3226465afedfdb@mail.gmail.com>

On Fri, Sep 05, 2008 at 03:38:31PM +0800, Steven Woody wrote:
> PS.  I just noticed, there is an error line when I run 'make' to get
> my rootfs image, it is:
>  ...
>  rootdir=/root/buildroot/project_build_arm/uclibc/root
>  table='target/generic/mini_device_table.txt'
>  /root/buildroot/build_arm/cramfs-1.1/mkcramfs: invalid option -- l
>  rm -f /root/buildroot/project_build_arm/uclibc/.fakeroot*
> 
> I checked, there is no a -l option for mkcramfs, but the buildroot
> does try to use it.  Anyway, the cramfs is created successfully, but I
> am not sure it is not a problem.

-l is for a little endian file system, so if it's producing a file
system with the wrong endianness, yes that's a big problem.

I'm assuming your target is little-endian. (By the way the
buildroot.config you attached to the next message was actually some sort
of configure log, not a buildroot configuration - so I couldn't check
that).

Your mkcramfs build must have got wrong, or you're missing the patches
or something. Specifically you must have
target/cramfs/cramfs-02-endian.patch - it's dated 2005 so I can't
believe it's just a case of an old version.

Can you check if you have that patch? Perhaps you can "make
cramfs-dirclean", then make again, and if you still see the problem then
post a build log from "make cramfs-dirclean cramfs".

It's unfortunate that mkcramfs doesn't bomb out when passed invalid
options..


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-09-05 13:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  8:02 [Buildroot] Login exited Steven Woody
2008-09-02  0:47 ` Steven Woody
2008-09-02  6:24   ` Emil Kruper
2008-09-02 11:26     ` Steven Woody
2008-09-02 13:07       ` Hamish Moffatt
2008-09-02 15:09         ` Steven Woody
2008-09-02 15:10           ` Steven Woody
2008-09-03  1:00             ` Hamish Moffatt
2008-09-03  0:59           ` Hamish Moffatt
2008-09-03  3:55             ` Steven Woody
     [not found]   ` <200809031950.49148.vda.linux@googlemail.com>
2008-09-04  1:50     ` Steven Woody
2008-09-04  2:00       ` Hamish Moffatt
2008-09-04  5:34         ` Steven Woody
2008-09-04 14:29           ` Hamish Moffatt
2008-09-04 15:49             ` Steven Woody
2008-09-05  1:07               ` Hamish Moffatt
2008-09-05  7:38                 ` Steven Woody
2008-09-05 13:09                   ` Hamish Moffatt [this message]
2008-09-07  5:44                     ` Steven Woody

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=20080905130918.GB31755@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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.