title: Installing WordNet on Linux (Ubuntu trusty)
body: <p>I am trying to install <a href="https://wordnet.princeton.edu/wordnet/download/current-version/" rel="nofollow">WordNet-3.0</a> on Ubuntu trusty.</p>
  
  <p>When I ran configure script, I got:</p>
  
  <pre><code>checking for Tcl configuration... configure: WARNING: Can't find Tcl 
  configuration definitions  
  </code></pre>
  
  <p>It's a warning, but still, configuration stopped without creating makefiles.</p>
  
  <p>So I <a href="http://www.tcl.tk/software/tcltk/download.html" rel="nofollow">downloaded</a> and installed tcl8.6.1, then ran the configure script again, but I got:</p>
  
  <pre><code>checking for Tcl configuration... found /usr/local/lib/tclConfig.sh
  checking for Tk configuration... configure: WARNING: Can't find Tk 
  configuration definitions  
  </code></pre>
  
  <p>So I <a href="http://www.tcl.tk/software/tcltk/download.html" rel="nofollow">downloaded</a> and installed tk8.6.1, then ran the configure script again, but the warning message persisted.</p>
  
  <p>I found <code>tkConfig.sh</code> in <code>~/Downloads/tk8.6.1/unix/</code>, so I copied it to /usr/local/lib, ran the script again, but I got:</p>
  
  <pre><code>checking for Tcl configuration... found /usr/local/lib/tclConfig.sh
  checking for Tk configuration... found /usr/local/lib/tkConfig.sh
  checking for existence of /usr/local/lib/tclConfig.sh... loading
  checking for existence of /usr/local/lib/tkConfig.sh... loading
  configure: creating ./config.status
  config.status: creating Makefile
  config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir setting
  config.status: creating dict/Makefile
  config.status: creating doc/Makefile
  config.status: creating doc/html/Makefile
  config.status: creating doc/man/Makefile
  config.status: creating doc/pdf/Makefile
  config.status: creating doc/ps/Makefile
  config.status: creating include/Makefile
  config.status: error: cannot find input file: `include/tk/Makefile.in'  
  </code></pre>
  
  <p>What shall I do? The configure script is a daunting 5755 lines long, I dare not tinker with it...</p>