[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mkfs.jffs2.c

On Sat, 26 April 2003 15:48:09 +1000, Michael Keating wrote:
> I am trying to compile JFFS2 support into my uClinux kernel 2.4...
> After fixing a few other issues, 

Do you have a patch for those? If the fixes are harmless for others
but help uClinux, they should go into CVS.

> I don't seem to be able to get past:
> m68k-elf-gcc -m5307 -DCONFIG_COLDFIRE -Os -g -fomit-frame-pointer -m5307
> -DCONFIG_COLDFIRE  -Dlinux -D__linux__ -Dunix -D__uClinux__ -DEMBED
> -I/home/michael/uClinux-dist/lib/uClibc/include
> -I/home/michael/uClinux-dist/lib/libm
> -I/home/michael/uClinux-dist/lib/libcrypt_old
> -I/home/michael/uClinux-dist -fno-builtin -msep-data
> -I/home/michael/uClinux-dist/linux-2.4.x/include
> -I/home/michael/uClinux-dist/lib/zlib -D__USE_BSD   -c -o mkfs.jffs2.o
> mkfs.jffs2.c
> mkfs.jffs2.c: In function `write_dirent':
> mkfs.jffs2.c:528: incompatible types in assignment
> Followed by lots and lots of 'incompatible types in assignment. I have
> downloaded the latest MTD snapshot and applied the patch, with no
> success.

Is line 528 the one marked below? In that case your compiler seems to
dislike something in the definition of error_msg(), but I am not sure

		parent = find_filesystem_entry(root, dir, S_IFDIR);
		if (parent == NULL) {
-->			error_msg ("skipping device_table entry '%s':
no parent directory!", name);	<---
			return 1;

A simple approach for the unafraid would be to simply remove all the
*error_msg* calls and live with it, but don't tell anyone I said that.

Is you cross-compiler and the necessary library availlable somewhere?
Possibly even as .deb? emdebian.sourceforge.net has only ppc and arm.


Anything that can go wrong, will.
-- Finagle's Law

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com