For Unix, use ./configure (or ./configure -prefix=$HOME/usr for an installation for a single user), make and finally make install or make install-strip, the latter for smaller executables without debugging information. If you want to make a RPM package, then replace the latest step by checkinstall or checkinstall make install-strip, supposing the package checkinstall on your machine. For other platforms, copy the relevant makefile (e.g. makefile.os2 for OS/2, or makefile.mgw or makefile.

The best place is definitely http://www.gnuplot.info. From there you find various pointers to other sites. The source distribution ("gnuplot-4.0.0.tar.gz" or a similar name) is available from the official distribution site and its mirrors. The main server is ftp.gnuplot.info in /pub/gnuplot/. This server is mirrored by several others, among those are of June 1999, the gnuplot distribution is also mirrored at the Comprehensive TeX Archive Network (CTAN) in the graphics/gnuplot directory. See similar questions...

Gnuplot is available for a number of platforms. These are: Unix (X11 and NeXTSTEP), Linux, VMS, OS/2, MS-DOS, Amiga, MS-Windows, OS-9/68k, Atari ST, BeOS, and Macintosh. You should be able to compile the gnuplot source more or less out of the box on any reasonable standard (ANSI/ISO C, POSIX) environment. Gnuplot is freeware authored by a collection of volunteers, who cannot make any legal statement about the compliance or non-compliance of gnuplot or its uses. See similar questions...

On unix-like systems, commands to gnuplot can be piped via stdin. Output from gnuplot's print command can be read via a named pipe. On M$ Windows platforms, due to the lacking standard input (stdin) in GUI programs, you need to use the helper program pgnuplot which should be included in your gnuplot for M$W distribution package. Reading gnuplot output may be impossible. See similar questions...

brings a new and exciting answer to this question: PAR, a "Cross-Platform Packaging and Deployment tool", originally developed by Autrijus Tang. Before PAR, the only public support for Perl/Tk "compilation" was in the Dr. See similar questions...

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

Check this out: Cobalt Raq2 - Building expect causes Fatal signal 11 in gcc [Kernel 2.0.34 MIPS , Redhat/Cobalt Release 4.0] Seems libieee.a is built oddly and gcc doesn't like it, neither expect nor tcl seem to actully need it, removing -lieee from the makefile allows it to compile, no undefined references, expect passes make test... (Maybe the needed functions are really in libm?) ps: tcl 8.2.1 needs the same fix to compile See similar questions...

REG) See the Kernel HOWTO for some information. Also, there are people at http://www.kernelnewbies.org/ who are usually willing to help. William Stearns) The Buildkernel script walks you through an entire kernel build, including downloading the necessary files, patching the source, building the kernel and modules, installing the lot into lilo, and optionally building pcmcia-cs, cipe, and freeswan code for that kernel. See similar questions...

You need Visual C++ 6 and Sleepycat db 3.1.17 (which you can get from here). If the compiler complains about missing db.h, then you don't have Sleepycat in a place where the compiler expects to find it. The project files for Outport are set up such that it expects the Sleepycat db zip file to be expanded in a directory called db-3.1.17, as in the diagram to the right. When you compile it, the binaries are created in win32/bin and win32/bind (release and debug respectively). See similar questions...

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. See similar questions...

Solaris (2.5 and up) has its own version of X in /usr/openwin, its own version of make in /usr/ccs/bin/make, and its own compiler (to be purchased separately) which, if you have it, is available in /opt/SUNWspro/bin. Solaris does not provide the XPM library, which is required for the Xaw client; it doesn't provide any of the stuff required for imlib, gdk and gtk, either, which is required to build the GTK+ client. See similar questions...

On Solaris, FreeBSD, and some other systems, the default make isn't GNU make. In order to compile with such a make you must either configure --disable-cvs-deps --disable-nls in order to disable the GNU make specific parts of the Makefile. See similar questions...

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. See similar questions...

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. See similar questions...