Make sure that if you don't already have Kogut installed that you're using the bootstrapped version of Kogut. Also make sure that you have a few basic Unix utilities: a C compiler, make, and a Bourne or Bash-style shell. If you're on Windows or Mac OS X, this probably means downloading Cygwin or Fink to get these tools. If all else fails, post your error to the Kogut mailing list.

The generated C programs made by Kogut are rather large, and this is not likely to change in the future. In fact, as further optimizations such as inlining are implemented, the output files will probably be even larger. But don't worry; this makes things much more efficient.

This might be either because it's completely unknown or because the specific environment (include files, OS version, et cetera) isn't explicitly handled. If this happens, you may need to port the server to your OS yourself. Some operating systems include a default C compiler that is either not ANSI C-compliant or suffers from other deficiencies. The usual recommendation in cases like this is to acquire, install, and use gcc.

All those "cannot find symbol" error messages mean that you do not have the Java servlet JAR file on your compiler's classpath, so it cannot find the servlet class files. The servlet JAR file is normally distributed with your servlet container. For Apache Tomcat it is a file named {CATALINA_HOME}/common/lib/servlet-api.jar. Add this to your compiler classpath as follows.

Kogut is an experimental programming language which supports functional and scripting-style programming, and a non-traditional flavor of object-oriented programming. Its semantics is most similar to Scheme or Dylan, but the syntax looks more like ML or Ruby.

If you are using a 64-bit OS, you need to add the -o32' option for the compiler, or use gcc. With the SGI compiler, you may also need to play with optimization. Some modules may have exhibit problems unless compiled with -O1' or even '-O0'. Script-Fu requires the POSIX-compliant regex functions, which SGI only supports with IRIX 6.2 and later versions. The GNU version of regex should work just fine, though, and is available at:

A servlet is a normal Java class, so when there are no custom constructors, there is an implicit default constructor with no arguments. Servlet containers typically use the Class.newInstance() method to load servlets, so you must be careful to add an explicit default constructor if you add non-default constructors.

Another common failure, for some WML pages, is seen when the wapbox log-file read something like "WML compiler: Parsing failed, no parsed document." Here, the libxml parser failed to understand the WML page, for some reason. Either the page is really malformed, or libxml has a problem. use 'xml-config --version' or 'rpm -q libxml', 'rpm -q libxml2', 'rpm -q libxml-devel' or 'rpm -q libxml2-devel' to find out whether libxml is installed on your system at all, and to see which version it is at.

The compiler found a symbol that it wasn't expecting.. for example, an extra paren on a complex if check, a semicolon placed after a function body header, a semicolon omitted from the previous line amongst others. The error is not always on the line mentioned by gcc, but may be the previous line. This error arises when you assign a pointer to a non-pointer variable.

There may be a number of reasons. Several peoples' answers are here. The most detailed answers, list first, are the best bets with their noted versions. According to resident Gimp on SOlaris guru Jim Harmon, more recent versions (0.99.25 on) should compile easily, but you may need to make a change in /usr/graphics/gtk-config.in: OLD: --libs) echo -L${exec_prefix}/lib -L/usr/openwin/lib -R/usr/openwin/lib \ -lgtk -lgdk -lglib -lXext -lX11 -lsocket -lnsl -lm ;; NEW: (subs.

Not an easy question to answer remotely. The wiki page in the developer's area includes solutions to some common problems.

This might be either because it's completely unknown or because the specific environment (include files, OS version, et cetera) isn't explicitly handled. If this happens, you may need to port the code to your OS yourself. Some operating systems include a default C compiler that is either not ANSI C-compliant or suffers from other deficiencies. The usual recommendation in cases like this is to acquire, install, and use gcc.

If you are using a 64-bit OS, you need to add the '-o32' option for the compiler, or use gcc. With the SGI compiler, you may also need to play with optimization. Some modules may have exhibit problems unless compiled with '-O1' or even '-O0'. Script-Fu requires the POSIX-compliant regex functions, which SGI only supports with IRIX 6.2 and later versions. The GNU version of regex should work just fine, though, and is available at: http://wuarchive.wustl.edu/systems/gnu/regex-0.12.tar.

Well, that depends. First make sure you are using the appropriate versions of FlightGear, SimGear, plib, zlib. If any of the packages are out of sync with the others, compilation may fail. The FlightGear Downloads page (http://flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Under JDK1.02, RMI implementations extend java.rmi.server.UnicastRemoteServer. This changed in JDK1.1 - you should now extend java.rmi.server.UnicastRemoteObject.

If you do, you'll need to get the source pcmcia-cs (if you haven't already). Once you have the source, you need to run the configure script for it. Directions on this are in the root directory of the pcmcia package. It will ask a question from where to get the configuration. It can deduce the settings from the running kernel/pcmcia modules. Once you have run the configure the config.h file that the WLAN drivers are looking for will be there and the compilation should work without errors.

There are several popular libraries which are often required by most free Linux games, Simple DirectMedia Layer (http://www.libsdl.org/), PLIB (http://plib.sourceforge.net/), ClanLIB (http://www.clanlib.org/), OpenAL (http://opensource.creative.com/), and Allegro (http://alleg.sourceforge.net). You might not have your XFree86 development headers.

You are probably missing popt.h, which newt needs to compile, it can be found in the 'popt' package. Check your distribution and see if they have popt, if not check Related Linux Packages to see where you can get it. You should have used CD-RW. ;) In the HOWTO, it gives instructions on how to create a test CD (one, not six).

Are you sure io_lib is installed where you think it is, and that the install path is seen by Perl (did you answer the questions during perl Makefile.PL ?)

If Fluent complains about not being able to find a compiler, then check to make sure that the compiler is properly installed. On Windows machines, it is possible to install the Visual C++ compiler without fully setting up the command line compiler (which Fluent needs to be able to find). During the installation process, you need to select the "register environment variables" option.

Kogut is object-oriented, just not in the traditional sense. Instead of classes, Kogut uses types. To hold instance variables, Kogut uses fields (ie. records or structs). For inheritance, Kogut uses subtyping. For methods, Kogut uses functions that dispatch on the types of their arguments. These are more like multimethod than traditional single-dispatch message-passing systems. For private methods, Kogut uses privacy in modules.

In a pure functional language like Haskell, functions are all referentially transparent. So if x == y, then f(x) == f(y). This may sound good at first, but it really causes a lot of problems. For example, say you want a function to generate random numbers. Typically, you would expect this to return a different result (usually) whenever it was called (with no arguments).

Unfortunately, one doesn't exist yet, but hold on; it shouldn't be too long. Right now, Kogut doesn't have that many users, but we expect more people to help eventually. The focus of the development of Kogut is making the code work correctly, not make it well-documented. Once Kogut has a stable codebase with tons of libraries, Marcin will spend more time on improving the documentation, but until then, it's up to the community.

Are you sure io_lib is installed where you think it is, and that the install path is seen by Perl (did you answer the questions during perl Makefile.PL ?)

What is the ->template, .template and ::template syntax about? Some older/broken compilers require that all the template arguments to a function template be used in the function's parameter list: template <typename T, typename U> T foo(T arg1, U arg2); // ok, both T and U used template <typename T, typename U> T bar(U arg1); // some compilers reject because // T only appears in the return type The Standard however allows this (although very early drafts did not).

There are several popular libraries which are often required by most free Linux games, Simple DirectMedia Layer (http://www.libsdl.org/), PLIB (http://plib.sourceforge.net/), ClanLIB (http://www.clanlib.org/), OpenAL (http://www.openal.org/), and Allegro (http://alleg.sourceforge.net). You might not have your XFree86 development headers.

brings a new and exciting answer to this question: PAR, a "Cross-Platform Packaging and Deployment tool", originally developed by Autrijus Tang. Before PAR, the only public support for Perl/Tk "compilation" was in the Dr.

Edit the code and remove the arguments to setpgrp. Or upgrade to Expect 5.31 (or later) which adapts automatically.

Check this out: Cobalt Raq2 - Building expect causes Fatal signal 11 in gcc [Kernel 2.0.34 MIPS , Redhat/Cobalt Release 4.0] Seems libieee.a is built oddly and gcc doesn't like it, neither expect nor tcl seem to actully need it, removing -lieee from the makefile allows it to compile, no undefined references, expect passes make test... (Maybe the needed functions are really in libm?) ps: tcl 8.2.1 needs the same fix to compile