Skip to main content

Installing SRILM 156 in Ubuntu 8.04

0. untar the source distribution in SRILM_DIR

1. set the environment variable
bash> export SRILM=SRILM_DIR

2. check the gcc version and the location of tcl library
e.g.
bash> gcc --version
bash> which gcc
bash> whereis tcl

3. edit the common/Makefile.machine.i686-gcc4

bash> chmod u+rwx Makefile.machine.i686-gcc4
bash> emacs -nw Makefile.machine.i686-gcc4
# GCC_FLAGS = -mtune=pentium3 -Wreturn-type -Wimplicit
# CC = /usr/local/lang/gcc-4.2.2/bin/gcc $(GCC_FLAGS)
# CXX = /usr/local/lang/gcc-4.2.2/bin/g++ $(GCC_FLAGS) -DINSTANTIATE_TEMPLATES
GCC_FLAGS = -mtune=pentium3 -Wreturn-type -Wimplicit
CC = /usr/bin/gcc $(GCC_FLAGS)
CXX = /usr/bin/g++ $(GCC_FLAGS) -DINSTANTIATE_TEMPLATES
...
#ADDITIONAL_INCLUDES =
ADDITIONAL_INCLUDES = -I/usr/include/tcl

4. Make
bash> make 1> logFile 2> errFile

5. That is it

Comments

Ferosh jacob said…
Check this link, they have the debian packages for almost all static LMs
http://cl.aist-nara.ac.jp/~eric-n/ubuntu-nlp/dists/dapper/nlp/
For srilm for jaundy,i86 it is
http://cl.aist-nara.ac.jp/~eric-n/ubuntu-nlp/pool/dapper/nlp/srilm_1.5.9-1nlp1~0dapper1_i386.deb

Popular posts from this blog

Web App Scaling with Flask Blueprint and Namespaces

A real-world Flask-RESTX-based API  may have multiple namespaces. The best practice for scaling a web application is to use a blueprint along with multiple namespace. The namespace is used to group a set of CRUD operations for a specific resource.  Blueprint can be used to combine (mixing) multiple namespaces. Here’s an example directory structure: project\ ├── app.py # Application file ├── apis #    ├── v20 # API directory    │   ├── __init__.py    │   ├── specs.py # API namespaces and REST methods    │   ├── steps.py # API namespaces and REST methods    └── v20bp.py # API blueprint file Here is an example app.py. Using a blue print allow you to mount your API on any url prefix. from flask import Flask from apis.v20bp import blueprint as api app = ...

Documenting REST API with Flask-Restx

This tutorial aims to use the Flask-restx library to implement and to document the REST API. Other similar libraries in the Flask framework include the   flask_resful and  Flask-restplus libraries.  The generated document is shown below.  All the operations are group into a default namespace. All the CRUD operations get, create, and update (except for the the delete operation) are displayed  below.  References -  https://flask-restx.readthedocs.io/en/latest/ -  https://preslav.me/2018/12/02/designing-well-structured-rest-apis-with-flask-restplus-part-1/ -  https://www.freecodecamp.org/news/structuring-a-flask-restplus-web-service-for-production-builds-c2ec676de563/ -  https://github.com/cosmic-byte/flask-restplus-boilerplate

Display and Print Source Codes

One can use either "a2ps" or "trueprint" to print source codes. Today, I am going to experiment with "trueprint". A decent source code printing program should have the following requirements: Indentation is done correctly. Smart Spacing to avoid leaving out one-two lines of codes in previous page. Be able to convert to pdf or ps Be able to print two pages on one side The following are several examples of using the "trueprint" function: bash >> trueprint --portrait --language=cxx --intelligent-line-wrap --four-up --page-break-after-function --no-cover-sheet --output=EMMUtil_cpp.ps EMMUtil.cpp bash >> ps2pdf EMMUtil_cpp.ps EMMUtil_cpp.pdf bash >> rm EMMUtil_cpp.ps Please read the man page for further explanations. good day !!!