public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: erik@hensema.net
Cc: dmitry-z@mail.ru, linux-kernel@vger.kernel.org,
	fuse-devel@lists.sourceforge.net
Subject: Re: [fuse-devel] Merging?
Date: Wed, 12 Jan 2005 20:56:27 +0100	[thread overview]
Message-ID: <E1CoobT-0002We-00@localhost> (raw)
In-Reply-To: <slrncuatr0.ego.erik@bender.home.hensema.net> (message from Erik Hensema on Wed, 12 Jan 2005 19:15:44 +0000 (UTC))

> I was using siefs, to mount the fs of my Siemens mobile phone
> (via serial cable). However it doesn't seem to work with the
> current fuse anymore.

The following patch makes it compile with FUSE 2.2-pre3 too.  You need
to run autoreconf after patching.

Not tested, since I don't have a Siemens phone.

Miklos

diff -ru siefs-0.4.orig/configure.in siefs-0.4/configure.in
--- siefs-0.4.orig/configure.in	2004-08-13 08:39:07.000000000 +0200
+++ siefs-0.4/configure.in	2005-01-12 20:40:20.000000000 +0100
@@ -39,14 +39,6 @@
 ])
 fi
 
-if ! grep -q '\(\*release\)' $fuseinst/include/fuse.h ; then
-	AC_MSG_RESULT([old])
-	AC_MSG_ERROR([
-*** You need fuse version 1.0 or later.
-*** Please go to http://sourceforge.net/projects/avf
-*** and download the latest version
-])
-fi
 AC_MSG_RESULT(${fuseinst})
 AC_SUBST(fuseinst)
 
diff -ru siefs-0.4.orig/siefs/Makefile.am siefs-0.4/siefs/Makefile.am
--- siefs-0.4.orig/siefs/Makefile.am	2004-08-13 08:45:30.000000000 +0200
+++ siefs-0.4/siefs/Makefile.am	2005-01-12 20:49:27.000000000 +0100
@@ -1,6 +1,6 @@
 ## Process this file with automake to produce Makefile.in
 
-CFLAGS = -I$(fuseinst)/include
+CFLAGS = -I$(fuseinst)/include -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=11
 
 bin_PROGRAMS = siefs slink
 


  reply	other threads:[~2005-01-12 20:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20041231T155940-548@post.gmane.org>
     [not found] ` <E1ClQi2-0004BO-00@dorka.pomaz.szeredi.hu>
2005-01-12 13:49   ` [fuse-devel] Merging? Miklos Szeredi
2005-01-12 14:31     ` Diego Calleja
2005-01-12 14:51       ` Miklos Szeredi
     [not found]         ` <200501122120.08217.vincenzo_mlRE.MOVE@yahoo.it>
2005-01-12 20:32           ` Miklos Szeredi
2005-01-13 14:08         ` Pavel Machek
2005-01-12 15:58       ` Florian Schanda
2005-01-12 16:16       ` Dobrica Pavlinusic
2005-01-14 11:37       ` Nix
2005-01-12 19:01     ` Andrew Morton
2005-01-12 19:15       ` Erik Hensema
2005-01-12 19:56         ` Miklos Szeredi [this message]
2005-01-12 20:15       ` Christian Axelsson
2005-01-12 20:19       ` Miklos Szeredi
2005-01-12 20:51       ` Diego Calleja
2005-01-12 21:15         ` Tomasz Torcz
2005-01-13 14:37       ` Pavel Machek
2005-01-17 17:01       ` Steve McIntyre
2005-01-18 22:23       ` Luca Ferroni
2005-01-12 19:44     ` Pavel Machek
2005-01-12 20:35       ` Miklos Szeredi
2005-01-12 20:56         ` Pavel Machek
2005-01-13  9:06           ` Miklos Szeredi
2005-01-13 10:52     ` Bernhard Schauer
2005-01-12 15:19 Hubert Tonneau
  -- strict thread matches above, loose matches on Subject: below --
2005-01-12 21:33 Vincenzo Ciancia
2005-01-12 23:19 ` Yaroslav Rastrigin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1CoobT-0002We-00@localhost \
    --to=miklos@szeredi.hu \
    --cc=dmitry-z@mail.ru \
    --cc=erik@hensema.net \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox