Difference between revisions of "Installation troubleshooting"

From Apertium
Jump to navigation Jump to search
Line 15: Line 15:
 
 
 
==Errors==
 
==Errors==
  +
  +
===Package not found===
  +
  +
During the configure script:
  +
  +
<pre>
  +
checking pkg-config is at least version 0.9.0... yes
  +
checking for APERTIUM... configure: error: Package requirements (apertium-3.0 >= 3.0.0) were not met:
  +
  +
No package 'apertium-3.0' found
  +
  +
Consider adjusting the PKG_CONFIG_PATH environment variable if you
  +
installed software in a non-standard prefix.
  +
  +
Alternatively, you may set the environment variables APERTIUM_CFLAGS
  +
and APERTIUM_LIBS to avoid the need to call pkg-config.
  +
See the pkg-config man page for more details.
  +
</pre>
  +
  +
This is because the language pair data cannot find the <code>apertium-3.0.pc</code> file. If you have installed Apertium in a non-standard prefix (or sometimes even <code>/usr/local</code>) the configure script will not be able to find it.
  +
  +
First find the location of this file (it should be in <code>$(PREFIX)/lib/pkgconfig</code> and then run this command:
  +
  +
<pre>
  +
$ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
  +
</pre>
  +
  +
Replace <code>/usr/local</code> with the appropriate prefix.
   
 
===Shared libraries===
 
===Shared libraries===

Revision as of 11:25, 28 December 2007

Installing

To be added

Using

You no longer need to specify the language pair directory, so when you've installed, just do:

$ cat /tmp/whatever | apertium <direction>

You can find more information in the manpages.

Errors

Package not found

During the configure script:

checking pkg-config is at least version 0.9.0... yes
checking for APERTIUM... configure: error: Package requirements (apertium-3.0 >= 3.0.0) were not met:

No package 'apertium-3.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables APERTIUM_CFLAGS
and APERTIUM_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

This is because the language pair data cannot find the apertium-3.0.pc file. If you have installed Apertium in a non-standard prefix (or sometimes even /usr/local) the configure script will not be able to find it.

First find the location of this file (it should be in $(PREFIX)/lib/pkgconfig and then run this command:

$ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig

Replace /usr/local with the appropriate prefix.

Shared libraries

lt-comp: error while loading shared libraries: liblttoolbox3-3.0.so.0: cannot 
open shared object file: No such file or directory

This is because lt-comp cannot find where your liblttoolbox libs are installed. You may need to do one of several things:

  1. If you have installed it in an odd location, do: export LD_LIBRARY_PATH=/path/to/weird/libdir
  2. If you have installed it in /usr/local
    1. Check to see if /usr/local/lib is in /etc/ld.so.conf, if it is, run ldconfig
    2. If it isn't, either add /usr/local/lib to /etc/ld.so.conf and re-run ldconfig, or do step 1.

PCRE

checking for pcreposix.h... no
configure: error: *** unable to locate pcreposix.h include file ***

You don't have the PCRE (Posix-compatible regular expressions) library header files installed, if you're in Debian or Ubuntu, do:

# apt-get install libpcre3-dev

Missing pair

$  echo "Eso es un test" | apertium es-ca
Error: Mode es-ca does not exist. Try one of:
README

Looks like you don't have any language pairs installed, did you run make install in the language pair directory?

If you did, email the output of

$ cat /usr/local/bin/apertium | grep -e APERTIUM -e DEFAULT

...obviously replace /usr/local/bin/apertium with the location of the $(prefix)/bin/apertium

and the steps you took to compile apertium to the apertium-stuff mailing list.