I wanted to test a problem with a removable filesystem, so I'm trying to build my own ntfs-3g binary. I didn't want to disturb my distribution's ntfs-3g, so I ran `./configure --enable-debug --prefix=/home/skierpage/programs/ntfs-3g-dev --exec-prefix=/home/skierpage/programs/ntfs-3g-dev`to make it install elsewhere.

That fails in `make install`:

I believe this is in error `./configure --help` says if I've set --exec-prefix then sbindir should be [EPREFIX/sbin].

I'm far from a Makefile expert, but the mistake might be in Makefile.am:
I think on all three lines $(DESTDIR)/sbin should be $(sbindir). If I change the generated Makefile to this, the symlinks get installed in a local sbin.

I realize that if key ntfs-3g files aren't in the root directory, then boot and recovery may be messed up. But please mention reasons to require files in the root and workarounds to place them elsewhere in the INSTALL file (with a pointer in the README) instead of leaving the file as the generic boilerplate documentation.

Thanks for this essential piece of software!

Hi,

To test some version of ntfs-3g without disturbing what is installed, you need not install the test version. After doing ./configure and make, just start the shell script which has been created in the src directory :

Defining specific directories to hold the driver and library is bound by constraints to interface with mount(8).

Regards

Jean-Pierre

That worked great for ntfs-3g-2010.10.2AR.1, thanks. It would be nice if this was mentioned in the README (part of "QUICK INSTALLATION" section) and INSTALL (new step 4) files before the boilerplate `make install`.

IMO the FSF boilerplate is inappropriate for most source packages; most people compiling a package are doing it to try something out, they don't want to replace what their distro gave them.

Hi,


Ok, I will do so for next release.

Regards

Jean-Pierre