Note that there are some explanatory texts on larger screens.

plurals
  1. POCannot install the Rubygem "Link Parser"
    text
    copied!<p>I would like to create a chatbot, and for that I want to use <a href="http://www.link.cs.cmu.edu/link/" rel="nofollow">Link Parser</a>, which is basically an engine that finds out the relations between words when looking at a sentence. </p> <p>There is a <a href="http://deveiate.org/projects/Ruby-LinkParser" rel="nofollow">Ruby wrapper</a> which I tried to install by using:</p> <pre><code>gem install linkparser </code></pre> <p>and also:</p> <pre><code>gem install linkparser -- --with-link-grammar="C:\Users\Gebruiker\Downloads\Linkparsergrammar\linkgrammar4r-0.0.3" </code></pre> <p>However, I keep getting the following errors:</p> <pre><code>Temporarily enhancing PATH to include DevKit... Building native extensions. This could take a while... ERROR: Error installing linkparser: ERROR: Failed to build gem native extension. C:/Ruby193/bin/ruby.exe extconf.rb --with-link-grammar=C:\Users\Gebruiker\Downloads\Linkparsergrammar\linkgrammar4r-0.0.3 checking for pkg-config... no Couldn't find your pkg-config binary *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=C:/Ruby193/bin/ruby --with-link-grammar --with-pkg-config --without-pkg-config Gem files will remain installed in C:/Ruby193/lib/ruby/gems/1.9.1/gems/linkparser-1.1.3 for inspection. Results logged to C:/Ruby193/lib/ruby/gems/1.9.1/gems/linkparser-1.1.3/ext/gem_make.out </code></pre> <p>I am on Windows Vista 32bit, and using the newest Ruby (1.9.3-p125)</p> <p>Can somebody explain what's going on?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload