As Christian Magnusson points out, there still is a problem with configurin=
g FUSE-depedent file systems. We run into this problem routinely with OWFS.
From: Christian Magnusson=20
Date: Mar 27, 2006 1:11 PM
Subject: SV: [fuse-devel] Compiling with Fuse
To: Paul Alfille <paul.alfille@...>
That didn=E2=80=99t help very much=E2=80=A6
When I install fuse-2.5.2 without any extra parameters =E2=80=9C./configure=
; make all install=E2=80=9D on old server at home,
fuse.pc is installed under /usr/local/pkgconfig/fuse.pc, and include files =
are under /usr/local/include/fuse.
I bet several thousand other users have done that.
=E2=80=9C/usr/bin/pkg-config =E2=80=93cflags fuse=E2=80=9D only read the pc=
-files from /usr/lib/pkgconfig/* and then we never find the installation un=
The suggested solution only work if fuse installed with =E2=80=9C=E2=80=94p=
Fr=C3=A5n: Paul Alfille [mailto:paul.alfille@...]
Skickat: den 27 mars 2006 17:04
Till: Christian Magnusson
=C3=84mne: Fwd: [fuse-devel] Compiling with Fuse
Did you see this?
---------- Forwarded message ----------
From: Miklos Szeredi <miklos@...>
Date: Mar 27, 2006 3:52 AM
Subject: Re: [fuse-devel] Compiling with Fuse
Cc: palfille@..., fuse-devel@...
> > Now that fuse is becoming mainstream, included with many
> > distributions, what is the prefered paths for configuration files
> > to find fuse.h?
> `pkg-config --cflags fuse` ?
There's also an autoconf macro that does this:
which will set and substitute FUSE_CFLAGS and FUSE_LIBS.