Installation troubleshooting - Revision history

Unhammer: /* AP_CHECK_LING not found when running configure or autogen.sh */

2019-05-24T08:13:16Z

AP_CHECK_LING not found when running configure or autogen.sh

Unhammer: /* Warning: unsupported locale, fallback to "C"" */

2019-02-19T13:29:34Z

Warning: unsupported locale, fallback to "C""

Shardulc: GitHub migration

2018-03-09T03:10:26Z

GitHub migration

Francis Tyers at 22:08, 7 March 2018

2018-03-07T22:08:03Z

Irene: /* ISO C++1z does not allow 'register' storage */

2017-07-09T21:35:17Z

ISO C++1z does not allow 'register' storage

Irene: /* Compilation errors */

2017-07-09T21:12:19Z

Compilation errors

Mlforcada: /* When running configure script for Apertium */

2017-03-29T15:19:34Z

When running configure script for Apertium

Mlforcada: /* When running configure script for Apertium */

2017-03-29T15:18:08Z

When running configure script for Apertium

Unhammer: /* Conversion error */

2016-10-05T09:09:52Z

Conversion error

Unhammer: /* Conversion error */

2016-10-05T09:09:39Z

Conversion error

@@ Line 100: / Line 100: @@
 </pre>
 (or 3.2 or 3.3. or whatever)
+===mv: cannot stat 'foo-bar.mode': No such file or directory===
+If you see
+<pre>
+modes=`xmllint --xpath '//mode[@install="yes"]/@name' modes.xml | sed 's/ *name="\([^"]*\)"/\1.mode /g'`; \
+        if test -n "$modes"; then mv $modes modes/; fi
+mv: cannot stat 'sme-nob.mode': No such file or directory
+make: *** [Makefile:695: modes/sme-nob.mode] Error 1
+</pre>
+you may have an outdated aclocal.m4/apertium.m4. Ensure you have the newest version of apertium (sudo apt update && sudo apt upgrade) and re-run
+<pre>
+$ ./autogen.sh --with-lang1=../apertium-foo # etc.
+</pre>
+(or, if you don't want to type in all that with-lang stuff, it may be enough to just do <code>$ aclocal</code>.)
 ===AP_CHECK_LING not found when running configure or autogen.sh===

@@ Line 319: / Line 319: @@
 when running a command, it means that your installation doesn't have the required locale enabled.
+Try:
-In Ubuntu at least, you can try something like
+<pre>export LC_ALL=C.UTF-8</pre>
-<pre>locale-gen es_EN.UTF-8</pre>  //replace es_EN.UTF-8 with whichever locale you should have installed
-For example, if
+That should work on all newer systems.
-<pre>LANG=es_ES.utf8 /usr/local/bin/apertium-deshtml /tmp/URLMH0f38</pre>
-gave you the error : 'Warning: unsupported locale, fallback to "C"'.
+If you have a very old system where the above does not work, you should upgrade.
-Then you could try
-<pre>locale-gen es_EN.UTF-8</pre>
-also see this link for an alternate method : http://tlug.dnho.net/node/237
+If you for some reason can't upgrade, you should reconsider your life choices before trying to generate a locale manually:
+<pre>locale-gen es_ES.UTF-8
+export LC_ALL=es_ES.utf8</pre>
 ===‘rpl_malloc’ was not declared in this scope===

@@ Line 1: / Line 1: @@
 [[Problèmes lors de l'installation|En français]]
-{{Github-migration-check}}
 {{TOCD}}
@@ Line 29: / Line 28: @@
 The clue here is the "..". Autotools is looking for an auxiliary file in the parent directory of this one. This will happen if you check out one project folder inside another one (e.g. check out the lttoolbox folder inside apertium-en-es, or similar).
-Solution: make a new subdirectory in your home folder and check out again there (e.g. mkdir ~/src && cd ~/src && svn co …)
+Solution: make a new subdirectory in your home folder and check out again there (e.g. mkdir ~/src && cd ~/src && git clone …)
 ===No package lttoolbox/apertium found===
@@ Line 115: / Line 114: @@
 If things worked before and then suddenly stopped working, re-running <code>autogen.sh</code> should be enough to fix it.
-Otherwise, '''first''', check that you have $prefix/share/aclocal/apertium.m4 (e.g. <code>ls /usr/local/share/aclocal/apertium.m4</code>). If you get "No such file or directory", do an <code>svn up</code> in apertium and make and make install. Now try autogen.sh again in the language pair. If it still doesn't find AP_CHECK_LING, you may have to tell autogen.sh where it is using one of the hacks below.
+Otherwise, '''first''', check that you have $prefix/share/aclocal/apertium.m4 (e.g. <code>ls /usr/local/share/aclocal/apertium.m4</code>). If you get "No such file or directory", do an <code>git pull</code> in apertium and make and make install. Now try autogen.sh again in the language pair. If it still doesn't find AP_CHECK_LING, you may have to tell autogen.sh where it is using one of the hacks below.

@@ Line 1: / Line 1: @@
 [[Problèmes lors de l'installation|En français]]
+{{Github-migration-check}}
 {{TOCD}}

@@ Line 396: / Line 396: @@
 Newer version  of c++ (c++1z/c++17) no longer supports usage of the <code>register</code> keyword. <code>Register</code> was orginally used to hint to the compiler to place a variable in a register for faster access, but most compilers today ignore that hint and decide for themselves. <br>
-The keyword is still present in apertium core. To locally remove the keyword from all files, do within the apertium/apertium directory:
+The keyword is still present in apertium core.
-<pre>
+Manually (using search-and-replace) removing the keyword works...
-perl -pi -w -e 's/register//g;' *.cc
-perl -pi -w -e 's/register//g;' *.h
-</pre>
 ==Runtime errors==

@@ Line 72: / Line 72: @@
 $ sudo apt-get install apertium-all-dev
 </pre>
+This may happen because packages change names so <code>dist-upgrade<code> may end up removing some to maintain old dependencies, and <code>apertium-all-dev</code> is often the one to get axed which leaves the rest not upgraded.
 ====When running configure script for language pair data====

@@ Line 64: / Line 64: @@
 Replace <code>/usr/local</code> with the appropriate prefix.
+If this kind of error happens even if you have updated Apertium from the nightly.dist repository, refreshing <code>
+apertium-all-dev</code> may work:
+<pre>
+$ sudo apt-get install apertium-all-dev
+</pre>
 ====When running configure script for language pair data====

@@ Line 401: / Line 401: @@
 ===<code>Conversion error</code>===
 The above [[#Error:_Unknown_error_matching_regexp_.28code_-16.29]] problem is now fixed in Apertium. However, files that were compiled before the patch was applied are not readable after the patch is applied.
 If you compiled the package yourself, the solution is to (hopefully for the last time now!) recompile the transfer files:

@@ Line 402: / Line 402: @@
 The above [[#Error:_Unknown_error_matching_regexp_.28code_-16.29]] problem is now fixed in Apertium. However, files that were compiled before the patch was applied are not readable after the patch is applied.
-The solution is to (hopefully for the last time now!) recompile the transfer files:
+If you compiled the package yourself, the solution is to (hopefully for the last time now!) recompile the transfer files:
 <pre>touch -c *t?x trules-*.xml && make</pre>
 (and optionally "make install" or "sudo make install")
+If you installed a language pair package (for example using apt-get), you should reinstall, making sure you reinstall the newest available package. See [[Installation]].
 ===Missing pair===