ruby - Jekyll not serving locally - 'could not find jekyll' -

-

i have little-to-no experience ruby, have been managing maintain jekyll site github. however, unknown reason, when cd website's directory , run jekyll serve following error:

could not find 'jekyll' (>= 0) among 7 total gem(s) (gem::missingspecerror)

here full error message:

/usr/local/cellar/ruby/2.4.1_1/lib/ruby/2.4.0/rubygems/dependency.rb:308:in `to_specs': not find 'jekyll' (>= 0) among 7 total gem(s) (gem::missingspecerror) checked in 'gem_path=/users/amin/.gem/ruby/2.4.0:/usr/local/lib/ruby/gems/2.4.0:/usr/local/cellar/ruby/2.4.1_1/lib/ruby/gems/2.4.0', execute `gem env` more information /usr/local/cellar/ruby/2.4.1_1/lib/ruby/2.4.0/rubygems/dependency.rb:320:in `to_spec' /usr/local/cellar/ruby/2.4.1_1/lib/ruby/2.4.0/rubygems/core_ext/kernel_gem.rb:65:in `gem' /usr/local/bin/jekyll:22:in `<main>'

trying gem env gives this, looks little messy:

rubygems environment:  - rubygems version: 2.4.5  - ruby version: 2.2.2 (2015-04-13 patchlevel 95) [x86_64-darwin15]  - installation directory: /usr/local/lib/ruby/gems/2.2.0  - ruby executable: /usr/local/opt/ruby/bin/ruby  - executable directory: /usr/local/bin  - spec cache directory: /users/amin/.gem/specs  - system configuration directory: /usr/local/cellar/ruby/2.2.2/etc  - rubygems platforms:    - ruby    - x86_64-darwin-15  - gem paths:    - /usr/local/lib/ruby/gems/2.2.0    - /users/amin/.gem/ruby/2.2.0    - /usr/local/cellar/ruby/2.2.2/lib/ruby/gems/2.2.0  - gem configuration:    - :update_sources => true    - :verbose => true    - :backtrace => false    - :bulk_threshold => 1000  - remote sources:    - https://rubygems.org/  - shell path:    - /users/amin/dropbox/code/google-cloud-platform/google-cloud-sdk/bin    - //anaconda/bin    - /opt/local/bin    - /opt/local/sbin    - /opt/local/bin    - /opt/local/sbin    - /library/frameworks/python.framework/versions/3.4/bin    - /usr/local/bin    - /usr/bin    - /bin    - /usr/sbin    - /sbin    - /opt/x11/bin    - /library/tex/texbin

my best guess jekyll should looking in usr/local/bin, , not usr/local/cellar, say, that's guess.

any advice on how working again appreciated!


Comments

Post a Comment

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

-
Image
so code works fine logger riddled message. there way rid of or suppress it? postannotation.swift class postannotation: mkpointannotation { //mark: properties let post: post //mark: initialization init(post: post) { self.post = post super.init() self.coordinate = cllocationcoordinate2d(latitude: post.latitude, longitude: post.longitude) self.title = post.title self.subtitle = post.timestring() } } adding annotation let annotation = postannotation(post: post) self.map.addannotation(annotation) func mapview func mapview(_ mapview: mkmapview, viewfor annotation: mkannotation) -> mkannotationview? { if annotation mkuserlocation { return nil } var annotationview = mapview.dequeuereusableannotationview(withidentifier: "pin") as? mkpinannotationview if annotationview == nil { annotationview = mkpinannotationview(annotation: annotation, reuseidentifier: "pin")
Read more

ZeroMQ on Windows, with Qt Creator -

-
i have installed zmq link given below on windows 7. http://zeromq.org/distro:microsoft-windows 1) have c++ project in qt-creator , i'm using zmq c++ binding (zhelpers.hpp etc). 2) have added .lib installed zmq folder qtcreator 3) while compiling, compiler looks _imp__zmq_verion, in .dll files present in .lib have __imp_zmq_version. 4) causing undefined reference zmq_version. anyone else faced problem , has solution ?
Read more

unity3d - Unity SceneManager.LoadScene quits application -

-
i have 2 different scenes 1 named 'main' , other 'game' both added scenes in load. when use scenemanager.loadscene("game"); works no problem when tried return main scene code if (input.getkeydown (keycode.escape)) { scenemanager.loadscene("main"); } strangely game quits. thanks. sorry interruption. somewhere on other script found code. if (input.getkeydown (keycode.escape)) { application.quit (); } that's bad, know...
Read more