Edit the code and remove the arguments to setpgrp. Or upgrade to Expect 5.31 (or later) which adapts automatically.

For versions prior to 1.5.2: Ensure that you are using Visual Studio 6 and have the latest service pack (at least sp5 - if you get error C2440 you need this), also ensure that you have the latest Microsoft Platform SDK (the one that comes with Visual Studio is dated and does not work with AxCrypt - you may receive errors about undefined symbols and also errors in templates used for safe Handle-handling in AxCrypt). For versions 1.5.

Currently, this type of summary information is not built into the compiler plugin, but it would be possible to add. If this feature is important to you, add your vote to MNG-1854. Currently, this is not possible. The main reason is that it's a non-trivial to determine whether an entire project's build is stale (the project here being one of the modules). It will be dependent on the phase being called, and the packaging of the particular module.

Probably because you haven't got your kernel sources configured correctly. Ensure that you have the sources in the expected locations (/usr/src/linux-2.x.x) and that you have a symlink from /lib/modules/2.x.x/build to that source folder)

Remember that when you apply a patch to the kernel, you must use the -p0 or -p1 option: otherwise, the patch may be misapplied. See the patch manual page for details. ld: unrecognized option -qmagic means that you should get a newer linker, from ftp://tsx-11.mit.edu/pub/linux/packages/GCC/, in the file binutils-2.8.1.0.1.bin.tar.gz.

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

Most compile and link errors stem from either a system that doesn't have the OpenGL development environment installed correctly, or failure to instruct the compiler where to find the include and library files. If you are encountering these problems in the Windows 9x/NT/2000 environment, read question 2.060 above to ensure that you've installed all files in their correct locations, and that you've correctly instructed the linker to find the .lib files.

xtiff.c: 63: Unable to find include file 'X11/Xaw/Form.h'. xtiff.c: 64: Unable to find include file 'X11/Xaw/List.h'. xtiff.c: 65: Unable to find include file 'X11/Xaw/Label.h'. Your application was written for X11R4/R5, and your Apollo only has X11R3. HP/Apollo now suppports X11R5 (see above on how to get it), although their idea of "support" doesn't include a number of shared libraries...

Your compiler version may not be supported/compatible for MATLAB. Please check this MATLAB page first and then specify the version number. For example, if g++ 3.3 is supported, replace CXX = g++ in the Makefile with CXX = g++-3.3

Make sure you have the DirectX SDK installed on your development host including the DirectShow SDK. Xvid's DirectShow filter has been developed using DirectX 8 SDK but also successfully compiled with DirectX 9 and DirectX 10 SDKs.

The TestXTuple sample requires that the tspaces.jar and xerces.jar files be in the classpath at runtime.

There were some incompatibilty issues. Get the latest version of graph.h and assign4_a.h and be sure that your declaration matches the revised one.

Sometime after 2.6.15, the upstream kernel changed from using the semaphores (i_sem) within the VFS layer to using mutexes (i_mutex). If your Linux distribution is running an older kernel, you may not be able to compile GFS. Your choices are: (1) upgrade your kernel to a newer one, or (2) downgrade your GFS or change the source code so that it uses semaphores like before. Older versions are available from CVS.

You are probably trying to compile something statically. You must either include stub routines for the _dl routines, or you must link the C library (or -ldl) dynamically. The source code below provides do-nothing stubs for the routines in question. libdl stubs -- John DiMarco <jdd@cs.toronto.

First of all, consider using the precompiled binary release of OpenSign. The applets in the binary releases are signed too, so you do not have to go purchase an object-signing certificate. However, if you still want to compile OpenSign yourself, you will need to install the following thirdparty dependencies Download the Java version and copy all files in libs/ to opensign-x-y-z-src/lib/.

This is normally indicative of hardware problems. (Re)making the world is an effective way to stress test your hardware, and will frequently throw up memory problems. These normally manifest themselves as the compiler mysteriously dying on receipt of strange signals. A sure indicator of this is if you can restart the make and it dies at a different point in the process.

To compile sources you will need Visual C++ 6.0 or a later version. Some files also require a new Platform SDK from microsoft.com: http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm or http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ If you are using MSVC, specify the SDK directories at the top of the "Include files" and "Library files" directory lists. These can be found under "Tools / Options / Directories". The latest Platform SDK is not compatible with MSVC6.

You probably also have <qedit.h> in your include file list. This is a known issue and the workaround is to split your code that uses VMR9 and the code that uses DES and related functions like IMediaDet into two separate source files. This means that you can't put either header file in a precompiled header such as stdafx.h. alternative solution was posted on the newsgroups by chadderack. He uses the #define below so that the conflicts are avoided: