Remember, as I stated earlier, we want to build everything as static binaries. This usually requires that we make some changes to the build process or invoke special switches for the config process.

Extract your SED source archive in your /scratch directory. From /scratch execute “tar xvzf /scratch/sed-xxx.xx.tar.gz” This assumes you have placed the archive in /scratch. If not, simply point to the correct location and extract the archive while in /scratch.

In the case of SED, we do not need to do anything during the configure process. At least, not that I was able to determine, but I have ADHDD! :D

Change to your SED src directory. In my case. “cd /scratch/sed-4.1.5/”

Then execute the following command.. ./configure

Once the configure process is complete, and provided there were no errors. Execute the following commands.

make clean

Then

make CC=“gcc -static”

Again, provided there were no errors during the build process you should be left with a file in /scratch/bash-x.x.x/sed named “sed”.

Verify that it was built statically by executing the following command. file /scratch/sed-x.x.x/sed/sed ( Fully path it to make sure it doesn't pick up on anything else. )

Your output should look like this. [root@demo sed-4.1.5]# file /scratch/sed-4.1.5/sed/sed/scratch/sed-4.1.5/sed/sed: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, statically linked, not stripped

If it looks like this, you must figure out what has gone wrong. It is more trouble than it's worth. ( IMH0 ) To build a bunch of dynamically linked packages that you have to find all the libs for.

/scratch/sed-4.1.5/sed/sed: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), not stripped ←- THIS IS BAD!