Re: [Moosefs-users] Question re: win32 client/access

[Travis H. <tra...@tr...>]

try adding the configure parameter  "--enable-mfsmount"

this will force the system prerequisite libraries to be present, 
otherwise the configure script will fail with the message "require 
.....  for mfsmount" .

The mfsmount uses the FUSE libraries and the zlibrary, and the system 
requires (in addition to the usual build tools like make, gcc), the 
developer packages of these libraries to be installed, so the headers 
are available.

By default the configure script will just decide to not bother trying to 
build the mfsmount client if one or more of these libraries / headers 
are not available, and continue to build the rest of it.

e.g. usually on my CentOS machines, I install these fuse-devel packages with

yum install fuse-devel  zlib-devel

and then (in your case)

./configure --prefix=/usr --sysconfdir=/etc/mfs
--localstatedir=/var/lib --with-default-user=mfs
--with-default-group=mfs --disable-mfschunkserver --enable-mfsmount


On 12-02-13 4:57 PM, JJ wrote:
> What would be the correct ./configure options|command to install
> mfsmount on a working mfsmaster?
>
> I tried ./configure --prefix=/usr --sysconfdir=/etc/mfs
> --localstatedir=/var/lib --with-default-user=mfs
> --with-default-group=mfs --disable-mfschunkserver&&  make
>
> with a find looking for it. Nothing.
>
> Tried fewer options (--disable*), no joy.
>
> Thank you for your time.
>
>
> JJ
> Support Engineer
> Cirrhus9.com
>