build fails on os x yosemite

[liamstask]

Looks like a declaration mismatch in the os x support header. I'm installing from homebrew, which worked fine for the same version on the previous os x rev. here's the build output: http://pastebin.com/2nXnvwaQ

[liamstask]

Gah - looks like this is the least of tup's problems. Homebrew/legacy-homebrew#31164 suggests that unsigned kexts (i.e., osxfuse) cannot be loaded, and there's not a short term solution in sight.

Perhaps it will make sense to get the dyld-based tup going on os x more quickly than previously planned ? :)

Otherwise, I can't easily downgrade, so this is a pretty big hurdle to running tup on my project.

[ehberger]

👍 - this is currently breaking our development process.

There is a signed osxfuse binary available from osxfuse directly, but I haven't been able to get homebrew to play nice with it yet.

[MikeMcQuaid]

• this is currently breaking our development process.

I'd recommend investigating these things before upgrading OS in future.

Although the build failure is something that should be fixed (probably by upstream)(whoops, thought this was on the Homebrew repo) @liamstask is right to say that you aren't going to be able to run unsigned kexts on 10.10 anyway.

[gorakhargosh]

I am using tup on Yosemite. https://osxfuse.github.io/ works. Please use it. :)

[ehberger]

as far as I can tell, this has been resolved, and this ticked can be closed. On OSX10 via homebrew the process (which uses a signed kext) is:

brew cask install osxfuse
brew install tup

[liamstask]

yep, looks like the compile fix was included upstream in 9812548 and brew cask can be used to install a signed version of osxfuse.

[MikeMcQuaid]

@ehberger FYI you can shorten that even more to brew install Caskroom/cask/osxfuse tup (even if Cask hasn't been already installed)