[MacPorts] #25759: macfuse fails to build user-space library due to libtool problems (was: sshfs cannot find 'fuse' but 'macfuse' is installed)

[MacPorts]

#25759: macfuse fails to build user-space library due to libtool problems
-------------------------------+--------------------------------------------
  Reporter:  george@…          |       Owner:  dports@…           
      Type:  defect            |      Status:  reopened           
  Priority:  Normal            |   Milestone:                     
 Component:  ports             |     Version:  1.9.1              
Resolution:                    |    Keywords:                     
      Port:  sshfs             |  
-------------------------------+--------------------------------------------
Changes (by dports@…):

  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 Replying to [comment:13 macosx12345@…]:
 >  Since I had run port in a screen session, I could look into the output
 of the first `port install` command and I noticed that there were lots of
 error messages like `../libtool: line 816: X--tag=CC: command not found`.
 At the end this prevented the compilation of the library, but port kept
 going with staging into destroot and installed the parts of the package
 that go into /Liibrary/Filesystems.
 >
 >  I attach the outputs of the two runs of `port -vu install macfuse`: the
 first one which "silently" failed and the second one which succeeded. HTH.

 Thanks, that's very helpful!

 It looks like what's going on in the failed run is that automake got rerun
 (not sure under what circumstances that happens, or why) without rerunning
 glibtoolize, and libtool fails because the installed version doesn't match
 the one that was used to prepare the source tarball.

 Forcing an autoreconf should fix this, but is a bit tricky since it's
 buried deep in the MacFUSE build process.

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