Eli   Documents Get Eli: Translator Construction Made Easy at SourceForge.net.
    Fast, secure and Free Open Source software downloads

General Information

 o Eli: Translator Construction Made Easy
 o Global Index
 o Frequently Asked Questions
 o Typical Eli Usage Errors

Tutorials

 o Quick Reference Card
 o Guide For new Eli Users
 o Release Notes of Eli
 o Tutorial on Name Analysis
 o Tutorial on Type Analysis
 o Typical Eli Usage Errors

Reference Manuals

 o User Interface
 o Eli products and parameters
 o LIDO Reference Manual
 o Typical Eli Usage Errors

Libraries

 o Eli library routines
 o Specification Module Library

Translation Tasks

 o Lexical analysis specification
 o Syntactic Analysis Manual
 o Computation in Trees

Tools

 o LIGA Control Language
 o Debugging Information for LIDO
 o Graphical ORder TOol

 o FunnelWeb User's Manual

 o Pattern-based Text Generator
 o Property Definition Language
 o Operator Identification Language
 o Tree Grammar Specification Language
 o Command Line Processing
 o COLA Options Reference Manual

 o Generating Unparsing Code

 o Monitoring a Processor's Execution

Administration

 o System Administration Guide

Mail Home

Frequently Asked Questions and Answers

Previous Chapter Next Chapter Table of Contents


Problems Reported by Implementors


Eli reports Remote IPC not available on this host

This error report indicates that Eli was unable to use the inter-process communication mechanism effectively. It is usually seen on Linux systems that are not connected to a network.

Eli's default inter-process communication mechanism is TCP/IP. If TCP/IP is not available, the environment variable ODIN_LOCALIPC can be set and Unix domain sockets will be used instead. Setting ODIN_LOCALIPC to 1 usually avoids the error report.


Eli reports Cannot connect to Odin server

This means that there is a problem with TCP/IP socket communication. It can occur in two situations: on initial installation of Eli and after some kind of abnormal termination. If it occurs on initial installation, you need to set the environment variable ODIN_LOCALIPC to 1 before invoking Eli. If it occurs after an abnormal termination, simply resetting the cache by means of the command "eli -r" should clear things up.

Requirements of Eli

> Does Eli require an installed gcc?
> Does Eli require an installed Tcl/Tk?
> Does Eli require an installed TeX?
> Does Eli require an installed Funnelweb?
> Does Eli require an installed Odin?
> Eli is only available on Unix machines!

Eli doesn't really require support tools beyond standard utilities you'll find on any Unix machine. Tcl/Tk isn't strictly required, but you miss out on a few features if you don't have it (the simplest info browser is implemented using Tcl/Tk as well as Eli's execution monitoring/debugging facilities). Most everything else is included in the distribution (including FunnelWeb and Odin). TeX is only required if you want to be able to format FunnelWeb documents using TeX. Eli doesn't rely on gcc at all. It uses whatever C compiler you have on your system.

While Eli itself has not been ported to systems other than Unix, the code that Eli generates is highly portable C code that can be compiled anywhere. (The generated C code can be compiled by a number of C++ compilers as well.) We have reports of people successfully compiling Eli generated code on Windows platforms.


What restrictions are placed on the Usage of Eli?

> Is professional support available and what is the licence agreement?

Eli is distributed under the terms of the GNU Public License. Code generated from Eli can for the most part be used without restriction.

We do not sell support, although we try to answer questions from users rapidly.


Configuration does not find the X-Window-System.

> Running ./configure on Slackware Linux 2.0.30 in XTerm (with DISPLAY=0:0)
> results in "checking for X... no", although X works ok for other
> applications.

The problem is not in running X applications, but in being able to compile X applications. You need the appropriate development include files and libraries.

If your X includes and libraries don't reside in the normal places, you may have to give configure some help. For example, you could invoke configure like this:

% ./configure --x-includes=/`somedir'/include --x-libraries=/`somedir'/lib
where `somedir' was the directory of your X installation.

If you believe your X installation is in a normal place, you could test out the following. To test the autoconf detection mechanism in isolation, you can do the following if you have autoconf installed:

  1. Go to some temporary directory and create a file called configure.in with the following contents:
       AC_INIT(configure.in)
       AC_PATH_X
       AC_OUTPUT()
    
  2. Run the command "autoconf". This will create a configure script in the directory.
  3. Run configure and see if it finds the X includes and libraries.



Previous Chapter Next Chapter Table of Contents