Hey - sorry if this question has been answered already (near as I can tell,=
it hasn't) but I've recently used svn to grab buildroot 1022, and when I=
make it, it ends up with only two modules in the build_arm_nofpu/root/bi=
n directory - busybox and lsmod.
I didn't notice any errors while making buildroot (unless I missed them in =
that endless stream of status notifications it spat out). I need to refla=
sh the file system on my gumstix, and currently the board can't boot to t=
he jffs2 image created by making this buildroot because of missing startu=
p modules, which, Dave says, is probably because there are only two files=
in this directory.
Does anyone know why when I make the buildroot this directory ends up with =
only these two files?
Thanks in advance,
From: Ryan Rapetti <rjrapetti@uc...> - 2006-07-10 16:50:21
Hmm, interesting. Actually, there are only two modules in mine, but a
whole stack of symlinks to busybox. So your problem appears to be in
the symlink creation process. The only possibility that comes to mind
is that you filesystem may not support symlinks. Windows FAT is the
only one I know that has this problem, so if you're on a native linux
filesystem it should work. The other posibility is that the program
"ln" (the command that creates a link) is an alias for something else
that doesn't act the way buildroot expects. You could check this by
giving the command "alias" (in bash). It will print all the aliases
active in your shell. Look for some thing like "alias ln = something_else"