You should use the Compaq compiler fort to compile both your fortran 77 and fortran 90 programs. C and C++ programs can be compiled with gcc or g++, respecively. To compile and link your MPI programs to the MPI libraries, use mpif77, mpif90, or mpicc. The mpi scripts use fort to compile and link your fortran MPI programs, and gcc or g++ to compile and link your MPI C or C++ programs. You can compile your codes on any machine, and you do not need to submit a job to compile your codes.

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.

When you build Solaris kernel modules use the same compiler that Sun used to build the OS. SunPro C is the only supported compiler. The following table gives the SunPro C compiler versions used to compile Solaris releases (in descending chronological order). The SunPro compiler does not work in compliant mode (-Xc), because the system header files are not fully compliant. Note: To ensure that compilers do not optimize away accesses to device registers, you must use volatile properly.

You should use pkg-config's PKG_CHECK_MODULES macro in your configure.in file, as demonstrated in the gtkmm_hello package. Since this is the single most asked question about running GTK+ programs, we'll answer it here, even though it is in the GTK+ FAQ. Make sure the /usr/local/lib (the default install dir for gtkmm) is properly configured in your /etc/ldconf or that it is in your LD_LIBRARY_PATH environment variable. Alternatively, specify another prefix when running configure.

I'm looking for new questions (with answers), better answers, or both. Please send suggestions to bug-octave@bevo.che.wisc.edu. If you have general questions about Octave, or need help for something that is not covered by the Octave manual or the FAQ, please use the help-octave@bevo.che.wisc.edu mailing list. This FAQ is intended to supplement, not replace, the Octave manual.

The AspectJ compiler or weaver is required at some point, but many people can use AspectJ without changing their build or deployment process significantly. For aspects that are not required to compile, you can use the AspectJ binary weaver, run at build-time or class-load-time. You can write aspects using the original code style (which must be compiled with the AspectJ compiler) or using the annotation style new in AspectJ 5 (which may be compiled with Javac or the AspectJ compiler).

How do I use scanf() and gets() functions with the PICC/PICC-18 compiler? A. The gets() function is not supplied by the compiler. Becuase gets() will get a string from a programer specified input, such as the serial port, it is easier for the programer to write this function then for it to be supplied in a library. There is a console get string function, cgets(), that will read string from an input using console formatting. The cgets() function is available in the cgets.

OpenGL programs are typically written in C and C++. You can also program OpenGL from Delphi (a Pascal-like language), Basic, Fortran, Ada, and others. Here are three sites with info on using OpenGL through Visual Basic: http://www.softoholic.bc.ca/opengl/down.htm, http://www.weihenstephan.de/~syring/ActiveX/, http://www.ieighty.net/~davepamn/colorcube.html.

Have a look at the install readme file that comes along with Xvid. It describes how to use the Xvid build scripts to compile Xvid with gcc under Linux or MinGW/CygWin. Xvid can also be compiled with Microsoft Visual C++ compiler using the provided project files included in the build directory. For other compilers you're pretty much on your own. It should be not very difficult however to make the code compile with a different compiler.

Almost any program with symbols can be probed. The "full support" described below is based on the debug information needed for source lines and target expressions. Support for additional architectures, operating systems and compilers is always in progress, so please contact if you don't see what you need here. Aprobe supports the Microsoft Visual C++ development system versions 6 and 7 but does not support .NET (Dynamic Runtime Model) applications.

Probably you are using the wrong C compiler. Grex has two compilers installed. cc is only used for building certain system executables. It is not ANSI standard, and it lacks certain standard include files. You need to use gcc instead. This is a fairly recent version of the Gnu C compiler. It is ANSI standard and very complete.

Opennap NG's current codebase is written in ISO C99. Unfortunately, most commercial C compilers do not (or not fully) support ISO C99 but rather define their own, proprietary and non-portable language extensions. GCC (GNU Compiler Collection) fully supports ISO C99. As it also makes some use of features unique to GCC, such as platform-dependent inline assembly, Opennap NG requires GCC as compiler.

The lines flagged by the assembler are the following, which use a combination of indirect operands and references to structure members: The MASM 5.11 assembler didn't mind this (and neither does Borland). But MASM 6.11 requires the use of the PTR operator to clarify the type of object pointed to by SI: If you're using ML.EXE, include the /Zm option when assembling. The complete command to assemble and link the program on page 269, for example, is: This message is generated when MASM.

First, download the sources. Then type make. It should produce nw802.o and usbvideo.o . Then modprobe videodev, insmod usbvideo.o & insmod nw802.o . Now the module is loaded. usbvideo.c & usbvideo.h are included in the CVS tree & in the packages but these files are actually part of the kernel tree. I included them because they may have not been built with your kernel. If you wish, you can copy these from /usr/src/linux/drivers/usb/ (eg. to get newer versions.

Cygwin/X uses the gcc compiler from the Free Software Foundation. Cygwin/X source code is mostly ANSI C compliant, but we cannot guarantee that Cygwin/X will compile with any other compiler, nor can we afford the time to support compilers other than gcc.

You do not compile the client and server source codes together, since the client is written in Java and the server is written in C. For the client, you can compile the source codes at any machine with Java compiler. For the server, you should compile the source codes in the machine that you intend to host the email system.

OpenSSL SHA-512 implementation depends on compiler support for 64-bit integer type. Few elder compilers [ULTRIX cc, SCO compiler to mention a couple] lack support for this and therefore are incapable of compiling the module in question. The recommendation is to disable SHA-512 by adding no-sha512 to ./config [or ./Configure] command line. Another possible alternative might be to switch to GCC.

Procmail as an integrated local mail delivery agent? (generic, sendmail, ZMailer, smail, SysV mailsurr)

You are changing the name of the output files with the %s substitution in the Additional Options entry in the project properties (Compiler tab). The solution is to ensure that the file name to be created by the compiler is quoted in the Additonal Options entry in the project properties. For instance: d="%s.abs"

Check your CLASSPATH variable, it should contain the file jcarnac.jar and full path to this file (i.e. c:\workspace\jcarnac\jcarnac.jar). Also, be sure that your JDK is the one that satisfies J/CarnacPro's system requirements. For "advanced" tutorials, that use XML parsers, you will also need xml4j.jar (XML parser from IBM ? alphaworks.ibm.com) in your CLASSPATH Check your CLASSPATH variable, it should contain file jcarnac.jar and full path to this file (i.e.

Please ensure this is not caused by using a broken toolchain, binutils or third party patch. A quick look at the Kautobuild for kernel you are trying to build should give some idea if the error is expected. Once all these things have been checked the issue should be reported to the community mailing list. When reporting these problems, always include as much information as possible as a minimum the full build line. This can be obtained by re-running the make with an additional argument: V=1

You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have some beta testers currently trying to compile with VC.NET, aka version 7.0, but we can't yet report complete success.) For the Cygwin and MinGW versions, you need the Cygwin environment, which comes with GCC, the compiler used for those versions. See section and do I need them to run XEmacs?, for more information on Cygwin and MinGW.

Gri requires a C++ compiler capable of handling the language feature called "templates," and it also needs the so-called "standard template library" (STL). Templates have been a feature of C++ since about 1994, and STL became part of the draft C++ library standard in early 1996. If your compiler vendor does not support templates or STL, you should obtain a newer compiler.

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.

Sure. However, you will be responsible for making any needed modifications to the provided code. The provided IntervalTimer will not work on other platforms since it makes calls into the Unix operating system. You can replace this by whatever system utility you have to get the time. Then by getting the time before and after the algorithm runs you can take their difference to determine the elapsed time. Just be sure that your procedure is the only process running.