On Wed, Nov 21, 2007 at 05:20:00PM +1000, Greg Ungerer wrote: [...] > >do not have execute permissions, resulting in errors and corrupted > >(zero-size) output files that are a bit hard to find if one is not > >familiar with uClinux. > > This is a problem specific to using the snapshot patches. > They do not get execute bits when created, whereas when > using the tar ball they will be unpackaged with the correct > permissions.
Ah, I have to admit I did not know about this limitation. > Try manually enabling the libz config in the applications/library > config options. Maybe the mtd-tools options need to select libz > in the Kconfig. I will try this later. > Well, you are using a development snapshot. A lot has changed > since the last stable release, and some issues still need to > be resolved. Thank you for calming me down. :-) In the earlier versions, I was having problems selecting some of the coldfire-specific drivers (compile errors in the kernel). I can not recall exactly which these were, because I tried different versions with different results. Maybe it was also a problem of using the gcc 3.4.3 from the eval board, things seem to be more stable with the newer toolchain. > I have put fixes in place for those scripts. Great! I will have to answer the other mail later - you are right, I did only take the busybox executable as the binary. Somehow I did not manage to simply take the romfs as the source for my initramfs, neither did I manage to correctly set up the kernel to take the cramfs (?) image as the root filesystem. I was thinking I could simply set it up as a mtd partition, and then give the kernel /dev/mtdx as the root filesystem, but it does not like it. Best regards, Wolfgang _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
