Re: 1.3.8 FreeBSD Compilation issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Definitely progressing. Everything compiles and installs (that is with
exporting this paths and forcing BUILD_FUSE_CLIENT="yes" in ./configure).
Now I get this in my debug logs:

2008-05-09 08:40:23 D [glusterfs.c:166:get_spec_fp] glusterfs: loading spec
from /tmp/gluster/etc/glusterfs/glusterfs-client.vol
2008-05-09 08:40:23 D [spec.y:107:new_section] parser: New node for 'brick1'
2008-05-09 08:40:23 D [xlator.c:115:xlator_set_type] xlator: attempt to load
file /usr/local/lib/glusterfs/1.3.8/xlator/protocol/client.so
2008-05-09 08:40:23 D [spec.y:127:section_type] parser:
Type:brick1:protocol/client
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:brick1:transport-type:tcp/client
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:brick1:remote-host:storage-0-1.genome.ucla.edu
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:brick1:remote-subvolume:brick
2008-05-09 08:40:23 D [spec.y:198:section_end] parser: end:brick1
2008-05-09 08:40:23 D [spec.y:107:new_section] parser: New node for
'brick-ns'
2008-05-09 08:40:23 D [xlator.c:115:xlator_set_type] xlator: attempt to load
file /usr/local/lib/glusterfs/1.3.8/xlator/protocol/client.so
2008-05-09 08:40:23 D [spec.y:127:section_type] parser:
Type:brick-ns:protocol/client
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:brick-ns:transport-type:tcp/client
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:brick-ns:remote-host:storage-0-1.genome.ucla.edu
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:brick-ns:remote-subvolume:brick-ns
2008-05-09 08:40:23 D [spec.y:198:section_end] parser: end:brick-ns
2008-05-09 08:40:23 D [spec.y:107:new_section] parser: New node for 'bricks'
2008-05-09 08:40:23 D [xlator.c:115:xlator_set_type] xlator: attempt to load
file /usr/local/lib/glusterfs/1.3.8/xlator/cluster/unify.so
2008-05-09 08:40:23 D [spec.y:127:section_type] parser:
Type:bricks:cluster/unify
2008-05-09 08:40:23 D [spec.y:185:section_sub] parser: child:bricks->brick1
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:bricks:scheduler:rr
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:bricks:namespace:brick-ns
2008-05-09 08:40:23 D [spec.y:141:section_option] parser:
Option:bricks:rr.limits.min-free-disk:5%
2008-05-09 08:40:23 D [spec.y:198:section_end] parser: end:bricks
2008-05-09 08:40:23 D [glusterfs.c:128:fuse_graph] glusterfs: setting option
mount-point to /tmp/1
2008-05-09 08:40:23 D [xlator.c:115:xlator_set_type] xlator: attempt to load
file /usr/local/lib/glusterfs/1.3.8/xlator/mount/fuse.so
2008-05-09 08:40:23 E [fuse-bridge.c:2611:init] glusterfs-fuse: fuse_mount
failed (No such file or directory)

2008-05-09 08:40:23 E [glusterfs.c:546:main] glusterfs: Initializing FUSE
failed

I really gotta learn some more C.

Jordan


On Thu, May 8, 2008 at 7:45 PM, Amar S. Tumballi <amar@xxxxxxxxxxxxx> wrote:

> -lconv should be added while linking fuse. or check with './configure
> --help' in fuse project that they have some options like '--disable-iconv'.
>
> try doing this before compiling glusterfs (just do 'make clean' before
> building again)
>
> export LDFLAGS="-L/usr/local/lib -liconv"
>
> Regards,
> Amar
>
>
> On Thu, May 8, 2008 at 7:40 PM, Jordan Mendler <jmendler@xxxxxxxx> wrote:
>
>> 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!
>>>
>>
>>
>
>
> --
> Amar Tumballi
> Gluster/GlusterFS Hacker
> [bulde on #gluster/irc.gnu.org]
> http://www.zresearch.com - Commoditizing Super Storage!
>


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux