An executable version of the code is included in the distribution. You only have to recompile the code if you need to change the size of the allocatable memory (see below). If your operating system is not included in the distribution list and not compatible to these systems, please contact Dr. Gwo for assistance. The source code for PC is pure Fortran 77 so that no C compiler or CPP preprocessor is needed. It does not contain the C input and output routines.

AspectJ 1.0 source code is available in an archive available with the 1.0 downloads. It contains instructions for building from sources. AspectJ 1.1+ source code is available through CVS using the CVS Root dev.eclipse.org:/cvsroot/tools. For more information on accessing the CVS tree at eclipse.org, see the documentation from http://eclipse.org. Find specific instructions in the AspectJ tree at org.aspectj/modules/build/readme-build-and-test-aspectj.html.

You need the standard GCC compiler. The standard method to build a binary file is to use the following commands: which will create a binary file, in /usr/local/lib/ called uae, which can be run. If you want the program installed elsewhere, use configure --prefix=<dir>. What out for errors during each part of the installation. You may need to install or upgrade other packages before it will completely install. Only some options are included in the default configuration, typing .

In order to compile Carrot2 you will need Java Software Developer Kit in version 1.4.2 or newer and Apache Ant. To build only one application, go to its directory (e.g. trunk/carrot2/applications/carrot2-demo-dcs) run Ant with the default target: ant build In the application's tmp/dist directory you'll find the compiled application. Please refer to the application's specific readme.txt files for instructions on how to run the application.

Source code is included for everything in the Debian system. Moreover, the license terms of most programs in the system require that source code be distributed along with the programs, or that an offer to provide the source code accompany the programs. The source code is distributed in the pool directory (see What's in the pool directory?, Section 5.10) together with all the architecture-specific binary directories.

Write a mail to the user's list describing the problem and providing information on the type of hardware, the flavour of operating system.

Only to help others like me ... I've successfully installed it with ./configure --enable-libsuffix=64 --prefix=/opt/kde3 --with-qt-dir=/usr/lib64/qt3/lib64 --with-qt-libraries=/usr/lib64/qt3/lib64 && make && su -c 'make install'

See the README (http://source.winehq.org/source/README) for instructions. Additionally, you may want to set the TMPDIR environment variable TMPDIR=~/tmp or TMPDIR=/tmp (if you are root).

If your operating system is from Sun or HP examine the Makefile and make any changes indicated inside. Copy the sample configuration file (sconfig.txt) to some convenient place such as /usr/local/lib/junkbuster/configfile or whatever you choose. The sample file has all the options commented out. You can remove the # character on any that you want, but it may be better to leave this until to later. Run it asynchronously: Decide on the options you really want, kill the process and start it again.

If you're not used to compiling code yourself, ask your ISP or administrator at work to provide it for you, or wait until we release an executable version. This is scheduled for mid-October 1997. Download zip file called ijb20.zip (~140k), then uncompress and unpack the zip archive using a tool like WinZip. Now the distribution (source and sample files) will be in a directory called ijb20.

Please install the "readline" and "readline-devel" RPMs/packages from your distro. Any 4.x version should be fine. You need to have installed the source of your currently running kernel. On most distros you simply have to install the "kernel-source" RPM/package.

The source code snapshots contain a file called "README.OS" (like Readme.win32, Readme.MacOS) that explains everything. The instructions for Linux systems are traditionally in the file called INSTALL.

Both platform invoke and COM interop use interop marshaling to accurately move method arguments between caller and callee and back, if required.

You will need to instruct the compiler where to find the cairo.h file, (generally something like -I /usr/include/cairo), and tell the linker where to find the cairo library and to link with it, (often something like -L /usr/lib -lcairo). But the exact flags and paths will depend on your compiler and your installation of cairo. To simplify this, cairo uses pkg-config which can help you determine the correct flags to use. If you have pkg-config installed, then you can compile the above hello.

It is necessary to compile the code from one of the myrinet cluster machines. A list of machine names can be found here: To log on to a machine, use either the secure shell command (ssh) or the remote shell command (rsh). For running on the myrinet-3 and myrinet-4 cluster, compile on a myrinet-3 or myrinet-4 machine. It is important to check that the processor is free (type "top" to make sure that the processor is not being used for a job).

Yes, but you are required to run the files provided with the benchmark if you are publishing results. As a general rule, modifying the source code is not allowed. Specific items (the load program, for example) can be modified to port the application to your environment. Areas where you are allowed to make changes are listed in the SPECjAppServer2004 Run and Reporting Rules. Any changes made must be disclosed in the submission file when submitting results.

The MediaPortal source code is about 160MB. However, SVN uses compression so only 66MB need to be downloaded, if you download the needed main trunk only. All other branches should not be downloaded.