Warning: Unable to load CarbonCore. FSEvents will be unavailable. #98

Closed
lwille opened this Issue Feb 26, 2010 · 6 comments

Comments

Projects
None yet
5 participants
@lwille

lwille commented Feb 26, 2010

I'm getting a warning "Warning: Unable to load CarbonCore. FSEvents will be unavailable." when starting compass -w with:
Rails 2.3.5
Gem 1.3.5
ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin10]

What does this warning mean? AFAIK, FSEvents is needed for watching file/folder changes - will Compass still work? CarbonCore.framework is available on my System.

@ttilley

This comment has been minimized.

Show comment Hide comment
@ttilley

ttilley Feb 27, 2010

Contributor

you're probably not using the OSX standard ruby, which includes rubycocoa by default (and is how FSSM hooks into the native filesystem-watching support). You -can- safely ignore this message... it's just a warning to let you know that the watch functionality is falling back to polling. The polling method is slower and will seriously kill your laptop battery power if you're not attached to a power source because it prevents your disks from spinning down (they're constantly being checked for changes).

Contributor

ttilley commented Feb 27, 2010

you're probably not using the OSX standard ruby, which includes rubycocoa by default (and is how FSSM hooks into the native filesystem-watching support). You -can- safely ignore this message... it's just a warning to let you know that the watch functionality is falling back to polling. The polling method is slower and will seriously kill your laptop battery power if you're not attached to a power source because it prevents your disks from spinning down (they're constantly being checked for changes).

@ttilley

This comment has been minimized.

Show comment Hide comment
@ttilley

ttilley Feb 27, 2010

Contributor

if you would, please close this ticket in compass and file it on FSSM (ttilley/fssm) as "dude, your warning messages suck". ;)

Contributor

ttilley commented Feb 27, 2010

if you would, please close this ticket in compass and file it on FSSM (ttilley/fssm) as "dude, your warning messages suck". ;)

@lwille

This comment has been minimized.

Show comment Hide comment
@lwille

lwille Feb 27, 2010

LOL ^^ thanks for the advice.

lwille commented Feb 27, 2010

LOL ^^ thanks for the advice.

@lessallan

This comment has been minimized.

Show comment Hide comment
@lessallan

lessallan Jun 17, 2010

Same issue here.

ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin9.5.0]
Rails 2.3.5
RubyCocoa is installed

Same issue here.

ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin9.5.0]
Rails 2.3.5
RubyCocoa is installed

@bartschuller

This comment has been minimized.

Show comment Hide comment
@bartschuller

bartschuller Jul 24, 2010

If you get this with the MacPorts version of ruby, then port installing rb-cocoa solves the problem.

If you get this with the MacPorts version of ruby, then port installing rb-cocoa solves the problem.

@migbar

This comment has been minimized.

Show comment Hide comment
@migbar

migbar Jul 30, 2010

ditto ... running Ruby from RVM

migbar commented Jul 30, 2010

ditto ... running Ruby from RVM

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment