[MacPorts] #17855: sshfs-2.2 build crashes

MacPorts noreply at macports.org
Mon Aug 24 01:16:21 PDT 2009


#17855: sshfs-2.2 build crashes
-------------------------------------------+--------------------------------
 Reporter:  martin.eisenhardt@…            |       Owner:  eridius@…           
     Type:  defect                         |      Status:  new                 
 Priority:  Normal                         |   Milestone:                      
Component:  ports                          |     Version:  1.7.0               
 Keywords:                                 |        Port:  sshfs-2.2           
-------------------------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Comment:

 Replying to [ticket:17855 martin.eisenhardt@…]:
 > Hi,
 >
 > when I try to install sshfs, the following happens:

 I see it too. I'm on Mac OS X 10.4.11 Intel. This is not the first error,
 of course; the first error is not shown because MacPorts only shows the
 last 30 or so lines of the error unless you use the debug switch. The
 first error is:

 {{{
 /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.  -D_REENTRANT
 -DFUSE_USE_VERSION=26 -DLIBDIR=\"/mp/lib\" -I/mp/include
 -DDARWIN_SEMAPHORE_COMPAT -D__FreeBSD__=10 -D_FILE_OFFSET_BITS=64
 -D_REENTRANT -I/usr/local/include/fuse -I/mp/include/glib-2.0
 -I/mp/lib/glib-2.0/include -I/mp/include   -O2 -Wall -W -c -o sshfs-
 sshfs.o `test -f 'sshfs.c' || echo './'`sshfs.c
 sshfs.c:26:25: error: fuse_darwin.h: No such file or directory
 }}}

 fuse_darwin.h is present on my system in ${prefix}/include/fuse/ but
 -I${prefix}/include/fuse does not appear in the above. Also, in sshfs.c,
 fuse_darwin.h is included as

 {{{
 #include "fuse_darwin.h"
 }}}

 This is strange because fuse_darwin.h is not part of the local header
 files of sshfs but is rather part of the "system headers" already
 installed using MacPorts, thus it should be referenced with <brackets> not
 "quotes". This include comes about as a result of the Mac OS X patch the
 port uses.

 I have attached a portfile patch which fixes it for me.

-- 
Ticket URL: <http://trac.macports.org/ticket/17855#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list