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.

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).

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:

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.

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 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.

A servlet is a program written in the Java programming language that runs on the server, as opposed to the browser (applets). Detailed information can be found at http://java.sun.com/products/servlet.

It is best to use an external stylesheet reference, so that you can edit your servlet and CSS rules independently.

A#7.5: There are two common sources of problems. The first is due to improper syntax in the inittab file. See the inittab(5) and initd(8) manual pages for the correct syntax. The second common problem is not due to the inittab file, but rather because the command you are trying to invoke is being invoked incorrectly. The way to check if this is the case is to run the command interactively and see what diagnostic messages appear.

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.

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.