I like to use the RPM package management system for keeping track of what software I've got installed on my machines. For various reasons I often end up making or recompiling packages for third-party software, and I make some of those files available here. There's no warranty and I won't provide support, but feel free to mail me feedback or suggestions.
These packages are built on a Red Hat Linux system using rpm 4, gcc 3, and glibc 2.2.5 (this means they'll work under Red Hat 7 and later). They are geared towards Red Hat systems and x86 architecture simply because that is what I use. I try to minimize Red Hat-specific dependencies, but I'm not likely to make RPMs for platforms other than x86 Linux. These are stable (not development) versions unless otherwise noted and include a minimum of patches.
You may need to force your browser to save downloaded files (e.g. by right-clicking a link and selecting "Save Target As"), since some browsers want to open .rpm files as RealAudio plug-in modules.
Analog is a popular log file analyzer made by Stephen Turner. This analog package doesn't install anything in the webroot by default; it's more secure and flexible that way. (Secure because the CGI program is not world accessible unless you explicitly make it so, flexible because you can link to the images from any number of webroots and get updated images automatically when upgrading.)
| Precompiled packages | analog-6.0-1.i386.rpm | 1.3 MB |
| analog-6.0-1.i586.rpm | 1.3 MB | |
| analog-6.0-1.i686.rpm | 1.3 MB | |
| analog-6.0-1.athlon.rpm | 1.3 MB | |
| Source package | analog-6.0-1.src.rpm | 1.5 MB |
GNU Binutils is a collection of binary utilities including the GNU linker (ld) and assembler (as).
| Precompiled package | binutils-2.15-1.i386.rpm | 3.1 MB |
| Static libraries (optional) | binutils-static-2.15-1.i386.rpm | 2.4 MB |
| Source package | binutils-2.15-1.src.rpm | 10.6 MB |
The GNU Compiler Collection is the compiler suite known as GCC. I started building these packages because the version of GCC supplied by Red Hat had lots of issues - a development version with a truly huge amount of patches. That's no longer a problem, and if you just need a compiler to build software you're probably better off with the official packages. However, as a developer I prefer using a "vanilla" GCC; I want my software to compile properly using a stable release with a minimum of patches. In particular, I don't want to rely on Red Hat bugfixes or track down bugs introduced by their patches.
The core packages gcc, cpp, and libgcc are the minimum required and will be sufficient for C development. You'll probably want some of the other shared libraries (like the standard C++ library libstdc++) since they'll be needed by other programs, but you won't need the additional language support packages unless you do development in those languages. Mixing i386, i586, and i686 packages from the GCC suite is not recommended, use the ones for your architecture.