netkittelnet compile fail. `exit' undeclared in main.cc 1783

On 29 Jun 2006, in the Usenet newsgroup comp.os.linux.misc, in article

Depending on your setup, you probably will find things up inusr-src-RedHat with the tarball and patches inusr-src-RedHat-SOURCES and the spec file inusr-src-RedHat-SPECS-. The .spec file tells how and in what order to run the patches and what is done to compile, install, or remove the package. The format is somewhat similar to a Makefile in concept.

Is this your patch, or just the materials that come in the source rpm? As the source comes out of the box, this should compile exactly the same binary that you would find in the equivalent .i386.rpm file or equal. If you are adding your patch, it would have to be added AFTER rpmbuild patches using the supplied patches.

The basic tarball is in the source rpm. This should be the same as the basic tarball from uk.linux.org, as well as the unmodified source from any package manager.

Glibc2 is a poor example, but using that - Red Hat 8 should have been updated to:

glibc-2.3.2-4.80.8.i386.rpm glibc-2.3.2-4.80.8.i686.rpm glibc-common-2.3.2-4.80.8.i386.rpm glibc-debug-2.3.2-4.80.8.i386.rpm glibc-debug-2.3.2-4.80.8.i686.rpm glibc-debug-static-2.3.2-4.80.8.i386.rpm glibc-devel-2.3.2-4.80.8.i386.rpm glibc-profile-2.3.2-4.80.8.i386.rpm glibc-utils-2.3.2-4.80.8.i386.rpm

The 'glibc-2.3.2' and 'glibc-common-2.3.2' packages have the parts of the libraries needed to run compiled binaries. The '-debug' packages are used when you are debugging the libraries. But that '-devel' is needed when you are compiling, or building. They have all the headers and .obj stuff you need for that task. Once the binaries are built-compiled-etc., then you can remove the -devel package if desired.

Old guy,