# SOLVED --Fatal Error building sites on one particular computer

**URL:** <https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495>\
**Category:** Help\
**Created:** [April 29, 2017, 12:41am UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495 "2017-04-29T00:41:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@bryan](https://talk.jekyllrb.com/u/bryan)\
**Post date:** [April 29, 2017, 12:41am UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/1 "2017-04-29T00:41:12Z")

</div>

I only get this error on one particular computer when I try to compile a site – any site. When I use the exact same files on a different computer, jekyll works fine. Can someone help me understand what I have done wrong with this computer setup?  
Liquid Exception: undefined method `includes_load_paths' for #<Jekyll::Site:0x00555e8dec00b8> in _layouts/default.html jekyll 3.1.6 | Error: undefined method`includes\_load\_paths’ for #Jekyll::Site:0x00555e8dec00b8

Thanks!

---

<div class="post-metadata">

**Author:** ![ckruse](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.jekyllrb.com/ckruse/32/16_2.png) [@ckruse](https://talk.jekyllrb.com/u/ckruse)\
**Post date:** [April 29, 2017, 1:58am UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/2 "2017-04-29T01:58:10Z")

</div>

A good place to start is to ensure you’re running the same versions of everything:

```
jekyll -v
ruby -v
gem -v

```

If versions check out, run `jekyll build --trace` and report back.

---

<div class="post-metadata">

**Author:** ![bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@bryan](https://talk.jekyllrb.com/u/bryan)\
**Post date:** [April 29, 2017, 3:05am UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/3 "2017-04-29T03:05:28Z")

</div>

Thanks for helping me.  
These are the outputs. I think they’re all up to date.

$ jekyll -v  
/var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/drops/document\_drop.rb:8: warning: already initialized constant Jekyll::Drops::DocumentDrop::NESTED\_OBJECT\_FIELD\_BLACKLIST  
/usr/lib/ruby/vendor\_ruby/jekyll/drops/document\_drop.rb:8: warning: previous definition of NESTED\_OBJECT\_FIELD\_BLACKLIST was here  
/var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/drops/drop.rb:8: warning: already initialized constant Jekyll::Drops::Drop::NON\_CONTENT\_METHODS  
/usr/lib/ruby/vendor\_ruby/jekyll/drops/drop.rb:8: warning: previous definition of NON\_CONTENT\_METHODS was here  
jekyll 3.1.6

Kitchen:~$ ruby -v  
ruby 2.3.3p222 (2016-11-21) [x86\_64-linux-gnu]

Kitchen:~$ gem -v  
2.6.11

var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/drops/document\_drop.rb:8: warning: already initialized constant Jekyll::Drops::DocumentDrop::NESTED\_OBJECT\_FIELD\_BLACKLIST  
/usr/lib/ruby/vendor\_ruby/jekyll/drops/document\_drop.rb:8: warning: previous definition of NESTED\_OBJECT\_FIELD\_BLACKLIST was here  
/var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/drops/drop.rb:8: warning: already initialized constant Jekyll::Drops::Drop::NON\_CONTENT\_METHODS  
/usr/lib/ruby/vendor\_ruby/jekyll/drops/drop.rb:8: warning: previous definition of NON\_CONTENT\_METHODS was here  
Configuration file: /home/bz/ownCloud/chicago-collective-master/\_config.yml  
Configuration file: /home/bz/ownCloud/chicago-collective-master/\_config.yml  
Source: /home/bz/ownCloud/chicago-collective-master  
Destination: /home/bz/ownCloud/chicago-collective-master/\_site  
Incremental build: disabled. Enable with --incremental  
Generating…  
Liquid Exception: undefined method `includes_load_paths' for #<Jekyll::Site:0x0055dd3367a0c8> in _layouts/default.html /var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/tags/include.rb:109:in`tag\_includes\_dirs’: undefined method `includes_load_paths' for #<Jekyll::Site:0x0055dd3367a0c8> (NoMethodError) from /var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/tags/include.rb:113:in`locate\_include\_file’  
from /var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/tags/include.rb:129:in `render' from /usr/lib/ruby/vendor_ruby/liquid/block.rb:151:in`render\_token’  
from /usr/lib/ruby/vendor\_ruby/liquid/profiler/hooks.rb:5:in `block in render_token_with_profiling' from /usr/lib/ruby/vendor_ruby/liquid/profiler.rb:80:in`profile\_token\_render’  
from /usr/lib/ruby/vendor\_ruby/liquid/profiler/hooks.rb:4:in `render_token_with_profiling' from /usr/lib/ruby/vendor_ruby/liquid/block.rb:135:in`block in render\_all’  
from /usr/lib/ruby/vendor\_ruby/liquid/block.rb:122:in `each' from /usr/lib/ruby/vendor_ruby/liquid/block.rb:122:in`render\_all’  
from /usr/lib/ruby/vendor\_ruby/liquid/block.rb:108:in `render' from /usr/lib/ruby/vendor_ruby/liquid/template.rb:210:in`block in render’  
from /usr/lib/ruby/vendor\_ruby/liquid/template.rb:262:in `with_profiling' from /usr/lib/ruby/vendor_ruby/liquid/template.rb:209:in`render’  
from /usr/lib/ruby/vendor\_ruby/liquid/template.rb:222:in `render!' from /usr/lib/ruby/vendor_ruby/jekyll/liquid_renderer/file.rb:28:in`block (2 levels) in render!'  
from /usr/lib/ruby/vendor\_ruby/jekyll/liquid\_renderer/file.rb:36:in `measure_bytes' from /usr/lib/ruby/vendor_ruby/jekyll/liquid_renderer/file.rb:27:in`block in render!'  
from /usr/lib/ruby/vendor\_ruby/jekyll/liquid\_renderer/file.rb:43:in `measure_time' from /usr/lib/ruby/vendor_ruby/jekyll/liquid_renderer/file.rb:26:in`render!‘  
from /usr/lib/ruby/vendor\_ruby/jekyll/renderer.rb:106:in `render_liquid' from /usr/lib/ruby/vendor_ruby/jekyll/renderer.rb:146:in`place\_in\_layouts’  
from /usr/lib/ruby/vendor\_ruby/jekyll/renderer.rb:70:in `run' from /usr/lib/ruby/vendor_ruby/jekyll/site.rb:179:in`block in render’  
from /usr/lib/ruby/vendor\_ruby/jekyll/site.rb:177:in `each' from /usr/lib/ruby/vendor_ruby/jekyll/site.rb:177:in`render’  
from /usr/lib/ruby/vendor\_ruby/jekyll/site.rb:59:in `process' from /usr/lib/ruby/vendor_ruby/jekyll/command.rb:26:in`process\_site’  
from /var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/commands/build.rb:63:in `build' from /var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/commands/build.rb:34:in`process’  
from /var/lib/gems/2.3.0/gems/jekyll-3.4.3/lib/jekyll/commands/serve.rb:37:in `block (2 levels) in init_with_program' from /usr/lib/ruby/vendor_ruby/mercenary/command.rb:220:in`block in execute’  
from /usr/lib/ruby/vendor\_ruby/mercenary/command.rb:220:in `each' from /usr/lib/ruby/vendor_ruby/mercenary/command.rb:220:in`execute’  
from /usr/lib/ruby/vendor\_ruby/mercenary/program.rb:42:in `go' from /usr/lib/ruby/vendor_ruby/mercenary.rb:19:in`program’  
from /var/lib/gems/2.3.0/gems/jekyll-3.4.3/exe/jekyll:13:in `<top (required)>' from /usr/local/bin/jekyll:22:in`load’  
from /usr/local/bin/jekyll:22:in `’

---

<div class="post-metadata">

**Author:** ![mmistakes](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.jekyllrb.com/mmistakes/32/2169_2.png) [@mmistakes](https://talk.jekyllrb.com/u/mmistakes)\
**Post date:** [April 29, 2017, 4:30pm UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/4 "2017-04-29T16:30:18Z")

</div>

Because Jekyll is a Ruby app you might want to look into using [Bundler](http://bundler.io/). What’s likely going on for is you have different gem versions installed across your machines and that’s causing the errors.

With Bundler it uses a `Gemfile` to manage all the gem dependencies which helps you keep all the versions in sync between development environments. The only change really is prepending Jekyll commands with `bundle exec`.

For a better write up on this check this post [https://learn.cloudcannon.com/jekyll/gemfiles-and-the-bundler/](https://learn.cloudcannon.com/jekyll/gemfiles-and-the-bundler/)

You’ll find a lot of these sorts of errors just go away. It really is the preferred way to use Jekyll.

---

<div class="post-metadata">

**Author:** ![bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@bryan](https://talk.jekyllrb.com/u/bryan)\
**Post date:** [April 29, 2017, 7:52pm UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/5 "2017-04-29T19:52:03Z")

</div>

Thanks so much for weighing in here. I really appreciate it. I watched the video, created a simple Gemfile and did the bundler install, but when I use bundle exec jekyll serve, it now says  
bundler: failed to load command: jekyll (/usr/local/bin/jekyll)  
LoadError: cannot load such file – /usr/share/rubygems-integration/all/gems/jekyll-3.1.6/bin/jekyll  
/usr/local/bin/jekyll:22:in `load' /usr/local/bin/jekyll:22:in`\<top (required)\>’

So there must be one last thing I am failing to do… Any thoughts?

---

<div class="post-metadata">

**Author:** ![mmistakes](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.jekyllrb.com/mmistakes/32/2169_2.png) [@mmistakes](https://talk.jekyllrb.com/u/mmistakes)\
**Post date:** [April 29, 2017, 8:52pm UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/6 "2017-04-29T20:52:26Z")

</div>

Try `bundle update jekyll`. Looks like you have an older version of Jekyll so updating might help.

---

<div class="post-metadata">

**Author:** ![bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@bryan](https://talk.jekyllrb.com/u/bryan)\
**Post date:** [April 29, 2017, 9:04pm UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/7 "2017-04-29T21:04:38Z")

</div>

i updated jekyll, but it still can’t find it.

---

<div class="post-metadata">

**Author:** ![bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@bryan](https://talk.jekyllrb.com/u/bryan)\
**Post date:** [April 30, 2017, 5:54pm UTC](https://talk.jekyllrb.com/t/solved-fatal-error-building-sites-on-one-particular-computer/495/8 "2017-04-30T17:54:28Z")

</div>

I discovered that I had installed jekyll with apt-get in addition to gem, and that is where the two were causing conflict. Once I uninstalled with apt-get and left the gem version, all conflicts went away.

Thanks for your assistance.
