Questions and answers related to FreeLing installation

The tagger is not opened

Submitted by Sebastià Salvà… on Fri, 11/13/2020 - 00:21

Dear all,

I was not able to install/run "Freeling 4.2 for iOS" from a package, so now I have installed it from a source.

However, when trying to run the analyzer, I get this message:

sebastia@Nou-MacBook-Air Fitxers Freeling % analyze -f ca-balear.cfg --outlv tagged rond.tag
libc++abi.dylib: terminating with uncaught exception of type std::invalid_argument: The tagger is not opened
/usr/local/bin/analyze: line 39: 77001 Abort trap: 6 $FREELING/bin/analyzer $param

Any help?

Problems compiling

Submitted by Mercedes on Fri, 10/09/2020 - 09:56

Hello! I have follow all the steps of the manual but I have the next problem when I do nmake install:

c:\Freeling\src\FreeLing-4.2\build>nmake install

Microsoft (R) Program Maintenance Utility Version 14.00.24210.0
Copyright (C) Microsoft Corporation. All rights reserved.

Import Error: DLL load failed

Submitted by gabriela123 on Thu, 04/09/2020 - 19:02

Hello, I am using Freeling 4.1 on Windows environment with MSVC 2015 and the equivalent versions of icu and boost. I installed Freeling from source and the python version that I used was 3.7.6 . When I try to test I get a error about DLL files, that says that the module is not found so I changed the path like it is recommended on freeling manual but it didn't work. The error is the following :

Can't reproduce example outcome

Submitted by GregReese on Thu, 05/09/2019 - 15:03

I installed the Windows version of FreeLing 4.1. When I try the usage example shown at
(with mytext.txt and myconfig.cfg also on that page), I get an output that is quite different than the expected results that the example shows. My output is:

El el DA0MS0 1
gato gato NCMS000 1
come comer VMIP3S0 0.978902 comer VMM02S0 0.021098
pescado pescado NCMS000 0.822581 pescar VMP00SM 0.177419
. . Fp 1

Submitted by giomach on Thu, 03/28/2019 - 13:24

After installing FreeLing 4.1 (under Windows 10), I run analyser, and the following files are reported missing: MSVCP140D.dll, VCRUNTIME140D.dll and ucrtbased.dll. These are Microsoft files, which are not available unless Visual Studio is installed. I believe that the "d" in the filenames stands for "debug", and it would seem that this binary has been made in debug mode. Was there a reason to use debug mode rather than "release" mode? In release mode, the files needed would be MSVCP140.dll etc, which can be downloaded from MS.