|
Hi Christian; Thanks for the response! I can tell you’ve been working on
Fuse/Owfs… ;-) Ok. So, yes, fuse is compiled with FUSE_USE_VERSION=26, and it’s not looking
at my local copy of the header files (it’s the same version anyway). That leaves the library
paths. I’ve been checking and rechecking that. Here’s the link
command for owfs: /serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/bin/mipsel-linux-uclibc-gcc
-I../include -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26
-I/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/usr/include
-I../../../owlib/src/include -fexceptions -Wall -W -Wundef -Wshadow
-Wpointer-arith -Wcast-qual -Wcast-align -Wconversion -Wstrict-prototypes
-Wredundant-decls -DOW_MT -Os -pipe -mips32 -mtune=mips32 -funit-at-a-time
-Wl,--rpath -Wl,/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/usr/lib
-Wl,--rpath -Wl,/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/lib -o
.libs/owfs owfs.o owfs_callback.o fuse_line.o
-L/serve/OpenWGT/trunk/openwrt/build_mipsel/owfs-2.3p7/module/owlib/src/c
-pthread
/serve/OpenWGT/trunk/openwrt/build_mipsel/owfs-2.3p7/module/owlib/src/c/.libs/libow.so
-L/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/usr/lib
-L/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/lib
/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/usr/lib/libfuse.so -lpthread
-lusb -Wl,--rpath -Wl,/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/lib
-Wl,--rpath -Wl,/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/usr/lib So, I’m specifying “/serve/OpenWGT/trunk/openwrt/staging_dir_mipsel/usr/lib/libfuse.so”,
which is the mipsel version I’ve generated compiling fuse. Do you or anyone else around know a lot
about “libtool” – I’m currently thinking that my
libtool config is where my problem lies, but I’ve never worked with
libtool, and it so far has been a bit on the non-obvious side of things. I
noticed that I’m NOT using the libfuse.la version of the lib, and I’m
thinking that this might have something to do with my problems. Thanks, Vince From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christian Magnusson How about compiling fuse
with FUSE_USE_VERSION=26 too? I bet you have missed that if you are
using the compat-functions. I have compiled
fuse-2.6-packages for unslung 6.8 (Linksys NSLU2) and fuse-2.4.2 for openwrt
rc5 (Linksys WRT54 etc), and those packages works perfect for me. You might have wrong
include paths or library paths when compiling (eg. They point to your local
fuse-installation, not the cross-compiled fuse installation). Try to look at the
read-access-time after cross-compiling fuse and owfs… ls –autrl
/usr/local/include/fuse/ /usr/include/fuse /Christian Från:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Vincent Fleming Well, I tracked down the “df” problem… I ported fuse-2.6.0pre2 to OpenWRT, but when I link libfuse
with owfs-2.3p7, the linker links owfs to the older backward-compatible
versions of some of the FUSE code. Specifically, it seems to be anything
where fuse uses .symver directives. In this case, statfs() had changed, and if I comment out
these: __asm__(".symver
fuse_reply_statfs_compat,[EMAIL PROTECTED]"); __asm__(".symver
fuse_reply_open_compat,[EMAIL PROTECTED]"); __asm__(".symver
fuse_lowlevel_new_compat,[EMAIL PROTECTED]"); from fuse_lowlevel.c, it works great. I had similar
problems with fuse_mount(). It seems to link incorrectly whenever a
.symver is used. I’m compiling owfs with FUSE_USE_VERSION=26. Any ideas on where this weirdness might be coming from? From what I can tell from the code, the compiler directive
should work… Thanks,
|
- [Owfs-developers] FUSE/OWFS link weirdness Vincent Fleming
- SV: [Owfs-developers] FUSE/OWFS link weirdness Christian Magnusson
- RE: [Owfs-developers] FUSE/OWFS link weirdness Vincent Fleming
