Home>

LocalBundle EXEC RAILS SAnd the following error came out.

/users/xxxxxx/project_name/vendor/bundle/ruby/2.6.0/gems/ffi-1.11.1/lib/ffi/library.rb:145:in `block in ffi_lib ':
COULD NOT OPEN LIBRARY '/USERS/XXXXXX/Project_name/vendor/bundle/ruby/2.6.0/gems/SASSC-2.2.1/ext/libsass.bundle':
dlopen (/users/xxxxx/project_name/vendor/bundle/ruby/2.6.0/gems/sassc-2.2.1/ext/libsass.bundle, 5): Image Not Found (LoaderRor)

As the error/Users/xxxxxx/project_name/vendor/bundle/ruby/2.6.0/gems/sassc-2.2.1/ext/Certainly if you go to seelibsass.bundleThere was no. (There is libsass)

Also within the work projectVENDOR /BUNDLE /RUBY /2.6.0 /GEMS /SASSC-2.2.1 /EXT /Even if you go to see the libsass.bundle, only libsass exists.

Even if I checked the solution such as this, I would like to advise if there is a knowledge of the solution or resolution procedure.

Thank you.

Environment

  • Mac OS Catalina
  • Ruby 2.6.4
  • gemBundle Install-Path Vendor /BundleInstallation

The first occurrence situation
After uninstalling MySQL, I came out at the time I reinstalled with Brew Install

Timed
Reinstalling Ruby (2.6.4) via RBENV

  • Answer # 1

    As follows, the following two ways were tried, and Rails Server now launched.

    • Bundle Update= > Gemfile.lock is updated= > Bundle EXEC Rails S
    • gemfile.lock erase= > Bundle Install-Path Vendor /Bundle= > Bundle EXEC Rails S
    I understand that the library referenced by GemFile.lock is likely to be the cause of the library, but it has not been elucidated.

    Even though he has not updated GEM, he thinks that GemFile.lock is not good to appear as a change difference.

    As

    , the answer will continue to be open.

  • Answer # 2

    As follows, the following two ways were tried, and Rails Server now launched.

    • Bundle Update= > Gemfile.lock is updated= > Bundle EXEC Rails S
    • gemfile.lock erase= > Bundle Install-Path Vendor /Bundle= > Bundle EXEC Rails S
    I understand that the library referenced by GemFile.lock is likely to be the cause of the library, but it has not been elucidated.

    Even though he has not updated GEM, he thinks that GemFile.lock is not good to appear as a change difference.

    As

    , the answer will continue to be open.