I tried that and couldn't get it to work. I played around quite a bit trying to hack the autoconf and makefiles into building fuse, but couldn't quite get it. Unfortunately I don't have that extensive of a background in either C or FreeBSD. Ultimately I got this in my logs, but not really sure where to go from here: 2008-05-08 18:41:11 E [xlator.c:120:xlator_set_type] xlator: dlopen(/usr/local/lib/glusterfs/1.3.8/xlator/mount/fuse.so): /usr/local/lib/libfuse.so.2: Undefined symbol "libiconv_open" If anyone has any suggestions on trying to get fuse mounted on BSD, I'd be happy to hear them. Thanks, Jordan On Thu, May 8, 2008 at 6:14 PM, Amar S. Tumballi <amar@xxxxxxxxxxxxx> wrote: > Yes, mostly I suspect the same, > Try adding these two commands, > > export CFLAGS="-I/usr/local/include" > export LDFLAGS="-L/usr/local/lib" > > Is there a path issue or something you would suggest trying to get gluster >> to recognize fuse and install the client? Also, if these will be effected by >> the patches that were committed, is there a particular snapshot that you >> think would both include this and likely be stable for production use? >> > Without testing things over FUSE on BSD its hard to give a warranty about > production use. But other things (like server export) should be stable > enough to use in production. > > >> >> Thanks so much, >> Jordan >> >> > > -- > Amar Tumballi > Gluster/GlusterFS Hacker > [bulde on #gluster/irc.gnu.org] > http://www.zresearch.com - Commoditizing Super Storage! >
