Bug#409253: FTBFS: error: macro "fuse_main" requires 4 arguments, but only 3 given
> Package: sshfs-fuse > Version: 1.6-1 > Severity: serious > > > Automatic build of sshfs-fuse_1.6-1 on em64t by sbuild/amd64 0.52 > ... > > make[2]: Entering directory `/build/tbm/sshfs-fuse-1.6' > > if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I. -D_REENTRANT > > -DFUSE_USE_VERSION=26 -DLIBDIR=\"/usr/lib\" -D_FILE_OFFSET_BITS=64 > > -I/usr/include/fuse -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > > -Wall -g -O2 -Wall -W -Icompat -MT sshfs-sshfs.o -MD -MP -MF > > ".deps/sshfs-sshfs.Tpo" -c -o sshfs-sshfs.o `test -f 'sshfs.c' || echo > > './'`sshfs.c; \ > > then mv -f ".deps/sshfs-sshfs.Tpo" ".deps/sshfs-sshfs.Po"; else rm -f > > ".deps/sshfs-sshfs.Tpo"; exit 1; fi > > sshfs.c:2352:65: error: macro "fuse_main" requires 4 arguments, but only 3 > > given > > sshfs.c: In function 'sshfs_opt_proc': > > sshfs.c:2352: error: 'fuse_main' undeclared (first use in this function) > > sshfs.c:2352: error: (Each undeclared identifier is reported only once > > sshfs.c:2352: error: for each function it appears in.) > > sshfs.c:2359:65: error: macro "fuse_main" requires 4 arguments, but only 3 > > given > > sshfs.c:2514:66: error: macro "fuse_main" requires 4 arguments, but only 3 > > given > > sshfs.c: In function 'main': > > sshfs.c:2514: error: 'fuse_main' undeclared (first use in this function) > > make[2]: *** [sshfs-sshfs.o] Error 1 Mea culpa. Please upgrade to 1.7 Thanks, Miklos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355827: sshfs: does not work
> ii fuse-utils 2.2.1-4sarge2 Filesystem in USErspace (utilities) > ii libfuse2 2.2.1-4sarge2 Filesystem in USErspace library > ii sshfs 1.1-1 filesystem client based on SSH File Transfer Try upgrading to FUSE-2.3 or later. FUSE module from the official kernel is not compatible with 2.2 or earlier FUSE releases. Miklos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355827: sshfs: does not work
> [EMAIL PROTECTED]:~% ls -l /usr/bin/fusermount > -rwsr-sr-x 1 root root 18376 2006-02-22 20:03 /usr/bin/fusermount > [EMAIL PROTECTED]:~% ls -l `which fusermount` > -rwsr-sr-x 1 root root 18376 2006-02-22 20:03 /usr/bin/fusermount > [EMAIL PROTECTED]:~% sudo chmod a+s /usr/bin/fusermount > [EMAIL PROTECTED]:~% ls -l /usr/bin/fusermount > -rwsr-sr-x 1 root root 18376 2006-02-22 20:03 /usr/bin/fusermount > [EMAIL PROTECTED]:~% > > Mmmm, that's weird. > /me guesses he is missing something totally obvious. OK, you don't need 'a+s' only 'u+s'. Anyway if you still get the same error, there's something else going on. Perhaps some security module enabled in the kernel? Miklos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355827: sshfs: does not work
> > The usual solution to this is > > > > chmod u+s /usr/bin/fusermount > > I tried this and doesnt work. What does the following show? ls -l /usr/bin/fusermount ls -l `which fusermount` Thanks, Miklos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355827: sshfs: does not work
> strace -s1024 -f -o sshfs.log sshfs [EMAIL PROTECTED]: dir/
>
> and search the mount system call in sshfs.log. Do you find something like
>
> mount("[EMAIL PROTECTED]:", "dir/", "fuse", MS_NOSUID|MS_NODEV,0x804d058) =
> -1 EINVAL (Invalid argument)
>
> Seems like fusermount and 2.6.15.6 (my kernel) don't want to talk to
> each other.
Hmm, I think this is different problem. Can you also show the "execve
fusermount ..." line in the strace? It looks as if it's some invalid
option, but strace doesn't show the mount options (the last argument).
Also, which package versions do you have?
Thanks,
Miklos
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#355827: sshfs: does not work
> Package: sshfs > Version: 1.2-1 > Severity: grave > Justification: renders package unusable > > After doing modprobe fuse, I try to do > > sshfs [EMAIL PROTECTED]: dir/ > > I give the passwd and then it says: > > fusermount: mount failed: Operation not permitted > > I don't know how to fix it. The usual solution to this is chmod u+s /usr/bin/fusermount I don't know what the official stand on this, Fenio can you enlighten us? Miklos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352631: SONAME
> Seems you've changed ABI in 2.5.x version of FUSE, but you left old SONAME
> version, which causes many issues when filesystems that still want to work
> with such library.
>
> Please take a look at http://bugs.debian.org/352631
>
> Could you please update your SONAME version to reflect ABI changes?
It's a bug in the versioning of the fuse_mount() symbol.
The following patch should fix it.
Thanks for the report,
Miklos
Index: lib/mount.c
===
RCS file: /cvsroot/fuse/fuse/lib/mount.c,v
retrieving revision 1.24
diff -u -r1.24 mount.c
--- lib/mount.c 9 Jan 2006 11:33:04 - 1.24
+++ lib/mount.c 19 Feb 2006 17:56:48 -
@@ -291,4 +291,4 @@
return fuse_mount_compat22(mountpoint, NULL);
}
-__asm__(".symver fuse_mount_compat22,fuse_mount@");
+__asm__(".symver fuse_mount_compat22,[EMAIL PROTECTED]");
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
