Hi Ken,
Thanks for your reply.
I will try to debug the problem.
Are there any pre-built ramdisk images for ARM (size less than/= 5MB) built
over other hosts (netbsd/linux) so that I test it on my target machine. This
will also confirm the problem is with the cross-compiled tools under Cygwin
(esp. nbmakefs).
Regards
--- On Fri, 3/13/09, Ken Hornstein <kenh%cmf.nrl.navy.mil@localhost> wrote:
From: Ken Hornstein <kenh%cmf.nrl.navy.mil@localhost>
Subject: Re: bad dir ino 4 at offset 80: mangled entry
To: "newbie" <mailto635%yahoo.com@localhost>
Cc: port-arm%netbsd.org@localhost, tech-toolchain%netbsd.org@localhost,
tech-kern%netbsd.org@localhost
Date: Friday, March 13, 2009, 11:49 AM
>I am using Cygwin to build the kernel + ramdisk image to be loaded onto a
>ARM based target machine.
You're not the first person to report this. It is clearly some issue with
the NetBSD tools that are cross-compiled under Cygwin (my guess is
that the problem lies in nbmakefs). From what I have seen, the kernel
is fine, it's just the ramdisk filesystem image is corrupt.
However, since no one has stepped up and debugged the problem, it has not
been fixed. I don't think many of the NetBSD hard-core developers
cross-compile under Cygwin. If you want to solve the problem, the best
way is to roll up your sleeves and track it down.
--Ken