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:

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.

To compile MrBayes 3.1 on a Silicon Graphics machine (running IRIX or Linux) you need to use the -lm flag at the end of the command line when linking. A typical compile session would look like this: gcc -DUNIX_VERSION -O3 -c -o mb.o mb.c gcc -DUNIX_VERSION -O3 -c -o mcmc.o mcmc.c gcc -DUNIX_VERSION -O3 -c -o bayes.o bayes.c gcc -DUNIX_VERSION -O3 -c -o command.o command.c gcc -DUNIX_VERSION -O3 -c -o mbmath.o mbmath.c gcc -DUNIX_VERSION -O3 -c -o model.o model.

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.

The "GNU Image Manipulation Program" (originally the General Image Manipulation Program) sired by Spencer Kimball & Peter Mattis. In their own words, "GIMP is our answer to the current lack of free (or at least reasonably priced) image manipulation software for Linux and UNIX in general." It is a raster editor, which means that it performs operations directly on the pixels that make up the image, and not a vector editor.

Some vendors of C products for 64-bit machines support 64-bit long ints.  Others fear that too much existing code depends on sizeof(int) == sizeof(long) == 32 bits, and introduce a new 64-bit long long int (or __longlong)  type instead. Programmers interested in writing portable code should therefore insulate their 64-bit type needs behind appropriate typedefs.

Samba will still remain available as an Open Source product (downloadable from the Web) for those customers who are satisfied with running unsupported software. However, for those customers who require supported software and will not run their business on "freeware," SGI Samba for IRIX offers customers a unique opportunity to use one of the best software suites available for serving Windows clients from UNIX servers with SGI worldwide support.

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.

The kernel and kernel modules are 64-bit on sparc64, userland is still 32-bit, and in fact the same as on sparc32. The conversion between native 32- and 64-bit function calls is being done via the kernel. Allthough you can compile a kernel with egcs64, you can't really use this compiler for building 64-bit userland binaries. See also "Why can't I compile certain software on my sparc64 ?" in Section 9.

Version 4.5 for the SGI is in COFF format. IRIX 6 requires an ELF format. MacroModel 5.0 and later are in the ELF format and can be used. If you want to run MacroModel under IRIX 6.X (X is any number), and have a pre 5.0 version, you must purchase the latest version of MacroModel. See ordering information for details.

You have an older run-time system than what PAPI was developed on. The fix is to change the definition to 'struct Dl_info'.

The STL from SGI, version 3.3, was the final merge of the STL codebase. The code in libstdc++ contains many fixes and changes, and the SGI code is no longer under active development. We expect that no future merges will take place. In particular, string is not from SGI and makes no use of their "rope" class (which is included as an optional extension), nor is valarray and some others. Classes like vector<> are, however we have made significant changes to them since then.

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's an experimental compatibility header that fixes most problems. However, bringing plug-ins over to Windows presents special challenges because some are unfriendly to the new threading architecture and hang CinePaint by starving the event loop. It's being worked on. Another area in development is gimp-print 16-bit support so that high fidelity art prints can be output.

Because there are font resolution problems on this system. I tried to add explicit font names on every button and menu. However, the font selection in the IRIX Xview port is buggy. Sometimes the correct font is selected, and sometimes something large and ugly. I guess this is some uninitialized variable problem in the Xview library. The very same window sometimes pops up with completely correct fonts, and sometimes not.

You probably just installed the graphics libraries. You also need to install the development portion as well; it's called the libgr source package. After installing that, GIMP should compile easily.

The 1.1 release will be out "soon" as part of IRIX 6.5; this release has some minor improvements and bug fixes over version 1.0.2 (which is currently shipping). We don't have any concrete information yet on the status of Cosmo Player 2.x for IRIX. We've also gotten lots of requests for a Linux player; there are no plans for this in the immediate future, but it may become more of a possibility as we get closer to releasing the IRIX version.

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.

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.

Many machines are stored in this area. 6' X 6" skids are the basis for these shelters that comfortably house 2 machines each. There is also under cover storage between some of the sheds and those parts machines have an additional tarp over them for protection. In the gararge there are usually about 4 machines waiting for use and that same number waiting for some sort of attention.