UPDATE: fusefs 1.1, libfuse 2.7.1, sshfs 1.8, and sshfs-gui 1.0.0

[takanori@…]

Patchfiles for macfuse 1.0.0. This version works well on Leopard. (I tested on both Tiger and Leopard.)

[takanori@…]

And here is a distfile. ('macfuse-1.0.0.tar.bz2')

​http://www.miko.org/~tatyana/temp_public/2007/11/07/macfuse-1.0.0.tar.bz2

If you wish you can create this file with the following command:

$ svn export ​http://macfuse.googlecode.com/svn/tags/macfuse-1.0.0 $ tar cvfj macfuse-1.0.0.tar.bz2 macfuse-1.0.0

[takanori@…]

MacFUSE 1.1 is out.

[takanori@…]

the new distfile is here: ​http://www.miko.org/~tatyana/temp_public/2007/11/13/macfuse-1.1.tar.bz2

[nox@…]

From my own experiments:

• dist_subdir fusefs should be added libfuse Portfile.
• We only need to add -DDARWIN_SEMAPHORE_COMPAT to the sshfs configure.cppflags
• sshfs complains about undefined symbols, it needs configure.ldflags-append -framework CoreFoundation.

[nox@…]

Every hook in sshfs-gui patchfiles are duplicated, thus the patch stage fails.

[nox@…]

The sshfs-gui post-destroot stage installs the sshfs.app's Contents folder inside /Applications/MacPorts

[takanori@…]

dist_subdir fusefs should be added libfuse Portfile.

Agreed. libfuse (and sshfs-gui) should have dist_subdir fusefs. Thanks for pointing it out!

We only need to add -DDARWIN_SEMAPHORE_COMPAT to the sshfs configure.cppflags

That may be true but, since these flags are being used to build the original binaries, I used them. (please check macfuse-1.1/tools/configure_for_macfuse.sh)

Of course as you say, it seems that there is no need to use -O and -g here. So I'll remove them later. Anyway Thanks!

sshfs complains about undefined symbols, it needs configure.ldflags-append -framework CoreFoundation.

I'll take a look later.

Every hook in sshfs-gui patchfiles are duplicated, thus the patch stage fails.

Well, I couldn't reproduce such problem. Please try:

$ sudo port clean

or maybe you are forgetting to update patchfiles. FYI, md5 of the patchfiles should be:

MD5 (fuse/sshfs-gui/files/patch-AppController.m.diff) = 2524a187bdab4205dc8ce4135a7dab57
MD5 (fuse/sshfs-gui/files/patch-sshfs.xcodeproj_project.pbxproj.diff) = 0b39168cb4037c61c897be06746bfb73

The sshfs-gui post-destroot stage installs the sshfs.app's Contents folder inside /Applications/MacPorts

Contents folder? It's so strange if it is true. I don't know why it happens...

[takanori@…]

sshfs complains about undefined symbols, it needs configure.ldflags-append -framework CoreFoundation.

I'll take a look later.

I could not reproduce this problem. (I think sshfs never use CoreFoundation. Thus, I cannot explain why this problem occurs on your mac.)

[takanori@…]

revision 1. (tested on 10.4.10/ppc and 10.5.0/ppc)

[nox@…]

Replying to takanori@macports.org:

dist_subdir fusefs should be added libfuse Portfile.

Agreed. libfuse (and sshfs-gui) should have dist_subdir fusefs. Thanks for pointing it out!

We only need to add -DDARWIN_SEMAPHORE_COMPAT to the sshfs configure.cppflags

That may be true but, since these flags are being used to build the original binaries, I used them. (please check macfuse-1.1/tools/configure_for_macfuse.sh)

Of course as you say, it seems that there is no need to use -O and -g here. So I'll remove them later. Anyway Thanks!

Oh, yes, you're right.

Every hook in sshfs-gui patchfiles are duplicated, thus the patch stage fails.

Well, I couldn't reproduce such problem. Please try:

$ sudo port clean

or maybe you are forgetting to update patchfiles. FYI, md5 of the patchfiles should be:

MD5 (fuse/sshfs-gui/files/patch-AppController.m.diff) = 2524a187bdab4205dc8ce4135a7dab57
MD5 (fuse/sshfs-gui/files/patch-sshfs.xcodeproj_project.pbxproj.diff) = 0b39168cb4037c61c897be06746bfb73

Again, my bad.

The sshfs-gui post-destroot stage installs the sshfs.app's Contents folder inside /Applications/MacPorts

Contents folder? It's so strange if it is true. I don't know why it happens...

copy calls file copy. From file(n) manpage:

If a directory is specified as a source, then the contents of the directory will be recursively copied into targetDir.

Replying to takanori@macports.org:

sshfs complains about undefined symbols, it needs configure.ldflags-append -framework CoreFoundation.

I'll take a look later.

I could not reproduce this problem. (I think sshfs never use CoreFoundation. Thus, I cannot explain why this problem occurs on your mac.)

Here's the build log:

--->  Configuring sshfs
DEBUG: Executing org.macports.configure (sshfs)
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Environment: CFLAGS='-pipe -O2 -D__FreeBSD__=10 -DDARWIN_SEMAPHORE_COMPAT -DSSH_NODELAY_WORKAROUND -D_POSIX_C_SOURCE=200112L' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2' CPP='/usr/bin/cpp-4.0' CXX='/usr/bin/g++-4.0' F90FLAGS='-pipe -O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-pipe -O2' OBJC='/usr/bin/gcc-4.0' INSTALL='/usr/bin/install' OBJCFLAGS='-pipe -O2' FFLAGS='-pipe -O2' CC='/usr/bin/gcc-4.0'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Users_N_Ox_src_MacPorts_trunk_dports_fuse_sshfs/work/sshfs-fuse-1.8" && ./configure --prefix=/opt/local --disable-dependency-tracking'
checking for a BSD-compatible install... /usr/bin/install
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... /usr/bin/gcc-4.0
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/gcc-4.0 accepts -g... yes
checking for /usr/bin/gcc-4.0 option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of /usr/bin/gcc-4.0... none
checking for library containing dlsym... none required
checking for pkg-config... /opt/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for SSHFS... yes
checking for fuse_opt_parse... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
DEBUG: Portfile changed since installation
--->  Building sshfs with target all
DEBUG: Executing org.macports.build (sshfs)
DEBUG: Environment: 
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Users_N_Ox_src_MacPorts_trunk_dports_fuse_sshfs/work/sshfs-fuse-1.8" && make all'
make  all-am
/usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.  -D_REENTRANT -DFUSE_USE_VERSION=26 -DLIBDIR=\"/opt/local/lib\" -I/opt/local/include -D__FreeBSD__=10 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -I/opt/local/include/fuse -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include   -pipe -O2 -D__FreeBSD__=10 -DDARWIN_SEMAPHORE_COMPAT -DSSH_NODELAY_WORKAROUND -D_POSIX_C_SOURCE=200112L -Wall -W -Icompat -c -o sshfs-sshfs.o `test -f 'sshfs.c' || echo './'`sshfs.c
sshfs.c: In function 'random_string':
sshfs.c:1743: warning: implicit declaration of function 'rand_r'
sshfs.c: At top level:
sshfs.c:2720: warning: 'main' takes only zero or two arguments
/usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.  -D_REENTRANT -DFUSE_USE_VERSION=26 -DLIBDIR=\"/opt/local/lib\" -I/opt/local/include -D__FreeBSD__=10 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -I/opt/local/include/fuse -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include   -pipe -O2 -D__FreeBSD__=10 -DDARWIN_SEMAPHORE_COMPAT -DSSH_NODELAY_WORKAROUND -D_POSIX_C_SOURCE=200112L -Wall -W -Icompat -c -o sshfs-cache.o `test -f 'cache.c' || echo './'`cache.c
/usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.  -D_REENTRANT -DFUSE_USE_VERSION=26 -DLIBDIR=\"/opt/local/lib\" -I/opt/local/include -D__FreeBSD__=10 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -I/opt/local/include/fuse -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include   -pipe -O2 -D__FreeBSD__=10 -DDARWIN_SEMAPHORE_COMPAT -DSSH_NODELAY_WORKAROUND -D_POSIX_C_SOURCE=200112L -Wall -W -Icompat -c -o sshfs-fuse_opt.o `test -f 'compat/fuse_opt.c' || echo './'`compat/fuse_opt.c
/usr/bin/gcc-4.0  -pipe -O2 -D__FreeBSD__=10 -DDARWIN_SEMAPHORE_COMPAT -DSSH_NODELAY_WORKAROUND -D_POSIX_C_SOURCE=200112L -Wall -W -Icompat  -L/opt/local/lib -o sshfs  sshfs-sshfs.o sshfs-cache.o sshfs-fuse_opt.o -L/opt/local/lib -lfuse -lgthread-2.0 -lglib-2.0 -lintl -liconv   
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning prebinding disabled because dependent library: /opt/local/lib/libgthread-2.0.0.dylib is not prebound
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
_CFDictionaryCreateMutable
_CFDictionarySetValue
_CFNotificationCenterGetDistributedCenter
_CFNotificationCenterPostNotification
_CFRelease
_CFStringCreateWithCString
_CFUserNotificationDisplayNotice
___CFStringMakeConstantString
_kCFAllocatorDefault
_kCFCopyStringDictionaryKeyCallBacks
_kCFTypeDictionaryValueCallBacks
collect2: ld returned 1 exit status
make[1]: *** [sshfs] Error 1
make: *** [all] Error 2

[takanori@…]

Replying to nox@macports.org:

The sshfs-gui post-destroot stage installs the sshfs.app's Contents folder inside /Applications/MacPorts

Contents folder? It's so strange if it is true. I don't know why it happens...

copy calls file copy. From file(n) manpage:

If a directory is specified as a source, then the contents of the directory will be recursively copied into targetDir.

Ah, I see. Then I'll fix the problem, though it didn't occur on my Mac.

sshfs complains about undefined symbols, it needs configure.ldflags-append -framework CoreFoundation.

I'll take a look later.

I could not reproduce this problem. (I think sshfs never use CoreFoundation. Thus, I cannot explain why this problem occurs on your mac.)

Here's the build log:

At last I could reproduce the same problem on Tiger. My bad!

[takanori@…]

revision 2. (I hope all issues are resolved)

[josh-macports@…]

These are all new upstream versions, so revision should be 0 (and thus you can actually just omit the revision lines entirely.)

[takanori@…]

Replying to josh-macports@root.id.au:

These are all new upstream versions, so revision should be 0 (and thus you can actually just omit the revision lines entirely.)

I wouldn't like to reset the revision number because here are some old revisions. Anyway, thanks for your comment.

[takanori@…]

committed in r31527-31530. Thanks nox for your help!

[(none)]

Milestone Port Updates deleted