Package: squashfs
Severity: normal
Tags: patch

When building 'squashfs' on amd64 with gcc-4.0,
I get the following error:

gcc -I. -Wall -g -O2 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o 
mksquashfs.o mksquashfs.c
mksquashfs.c: In function 'mangle':
mksquashfs.c:247: warning: pointer targets in passing argument 1 of 'compress2' 
differ in signedness
mksquashfs.c:247: warning: pointer targets in passing argument 3 of 'compress2' 
differ in signedness
mksquashfs.c: In function 'create_inode':
mksquashfs.c:489: error: invalid lvalue in assignment
mksquashfs.c:549: error: invalid lvalue in assignment

With the attached patch 'squashfs' can be compiled
on amd64 using gcc-4.0.

Regards
Andreas Jochens

diff -urN ../tmp-orig/squashfs-2.0/squashfs-tools/mksquashfs.c 
./squashfs-tools/mksquashfs.c
--- ../tmp-orig/squashfs-2.0/squashfs-tools/mksquashfs.c        2004-07-13 
19:24:23.000000000 +0200
+++ ./squashfs-tools/mksquashfs.c       2005-03-07 14:42:36.372252183 +0100
@@ -485,8 +485,8 @@
                int i;
                squashfs_reg_inode_header *reg = &inode_header.reg, *inodep;
 
-               inodep = (squashfs_reg_inode_header *) inode = 
get_inode(sizeof(*reg) +
-                       offset * sizeof(unsigned int));
+               inode = get_inode(sizeof(*reg) + offset * sizeof(unsigned int));
+               inodep = (squashfs_reg_inode_header *) inode;
                reg->mtime = buf.st_mtime;
                reg->file_size = byte_size;
                reg->start_block = start_block;
@@ -546,7 +546,8 @@
                        return SQUASHFS_INVALID;
                }
 
-               inodep = (squashfs_symlink_inode_header *) inode = 
get_inode(sizeof(*symlink) + byte);
+               inode = get_inode(sizeof(*symlink) + byte);
+               inodep = (squashfs_symlink_inode_header *) inode;
                symlink->symlink_size = byte;
                if(!swap)
                        memcpy((void *) inode, symlink, sizeof(*symlink));


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to