The automatically generated configure scripts, Makefiles, etc. have been recently removed in the CVS version, to avoid the 'blasted' M */Makefile.in CVS messages for developers. If you're using the CVS version, you need to create them manually by running the autogen.sh script included in the library directories. This script requires autoconf >= 2.13, automake >= 1.4. The libraries in CVS already come with the required libtool (>=1.

Besides, if you need to ask that question, then trust me, you don't want to be bothered. It's very very hard. ;)

If your operating system is from Sun or HP examine the Makefile and make any changes indicated inside. Copy the sample configuration file (junkbstr.ini, previously called sconfig.txt and other names in earlier releases) 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 later.

A .exe file (binary) is supplied with the source code, but if you prefer to compile it yourself here is the likely procedure. Most of these steps are repeated in our checklist for installation under Windows. First click here to download the zip file called ijb20.zip (~208k), then uncompress and unpack the zip archive using a tool like WinZip. Now the distribution (source and sample files) will be in a folder called ijb20.

LibGGI is a fast, simple, small and flexible user-space graphics library. Originally it was developed to access the graphics functionality KGI (the GGI kernel code) had provided. Support for different types of displays and hardware are provided by dynamically-loaded mini-libraries. Nowadays LibGGI is a very generic piece of software, that will run on about every platform that has remotely heard of POSIX (ports to other systems such as Win32 are underway) and on many display subsystems.

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.

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 (OS) is not included in the distribution list and not compatible to these systems, please contact Dr. Gwo for assistance. If you don't find the exact version of your OS in the distribution list, you may try a different version that is listed. For instance, the HBGC123D executable for SunOS 4.1.

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

While there is no converter available from Microsoft that will migrate source code from CVS or Subversion, ComponentSoftware (not affiliated with Microsoft) is offering CS-Converter for evaluation. From their press release: CS-Converter is a powerful and reliable conversion tool, used to migrate from various legacy version control systems (such as RCS, CVS, Subversion and Visual SourceSafe) to Microsoft Team Foundation Version Control (TFVC) system.

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.

So I got transcode from CVS and compiled it according to the directions in the INSTALL file, and now I (still) have some sort of problem. Join the transcode-users mailing list (see the Support section on the Main Page) and check the archive to see if your problem has been discussed at the mailing list before. If your problem is that transcode "hangs" without doing anything, that is a known problem which is hard to solve. Often running transcode this way: "env LD_ASSUME_KERNEL=2.4.0 transcode ..

C++ is a superset of something, we're not sure what. You can use a C++ compiler to compile C code, but the results may surprise you.

Yes! Put the command \includeonly{blah} in the preamble where blah.tex is one of the files mentioned in and \include commands in the document. This will keep the same .aux, .toc, .lof and so forth files and compile only blah. This goes much faster, especially for a long thesis with lots of figures. Multiple files can be used: \includeonly{blah,foo,blatz}. Normal astronomical referencing is usually in the form (Smith 1999). Instead, \citep causes it to come out (Smith, 1999).

The Instruction Set compiler project property controls the type of code generated by both compiler and assembler, it can be set to ARM or Thumb. The ARM/Thumb Interworking compiler project property instructs the compiler whether to produce code that supports calling between ARM and Thumb instruction sets.

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.

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.

Again site specific. Assuming you are using a unix-like operating system the least-common-denominator editor is probably pico, which you can run by typing at the command prompt. emacs and vi have (many) more features, but a harder learning curve. xemacs, if available, is pretty easy to use and has a lot of features. Eclipse, KDevelop, or Visual Studio may also be available and have many features. Ask your site director.

Excelsior JET (http://www.excelsior-usa.com/jet.html) - a commercial tool for compiling Java into native code (Windows/Linux)

Because LibGGI is designed to be simple, it only provides basic drawing functions and visual management. Some applications may need more sophiscated functionality. This is provided by extensions, which are attached to LibGGI visuals (displays). Extensions have full access to the internals of LibGGI and may implement advanced features such as 3D, while using LibGGI's flexible DL system.

Typing the following two lines in the Terminal will download the latest source code into the current directory. Do not enter a password when prompted, just hit return. cvs -z3 -d:pserver:anonymous@cvs.wirelessdriver.sourceforge.net:/cvsroot/wirelessdriver co WirelessDriver Visit the project development page for more information. You can also browse the cvs tree to find out whats changed recently.

get the integration token (this is necessary to avoid that other people start integrating at the same time. You might use a special hat for that ("integration hat"))

The code in CVS is development code, and might not even compile, and much less work. Please use releases if you want things to "work". The CVS-version is bleeding edge though and may have bug-fixes and features missing in releases. CVS is also where exciting things happen and where you can track day-to-day development.