|
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
