Differences

This shows you the differences between two versions of the page.

Link to this comparison view

appnotes:sed_-_build_instructions [2009/04/23 06:59]
jmcdowell created
appnotes:sed_-_build_instructions [2009/04/23 07:16]
jmcdowell
Line 3: Line 3:
 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. 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 have to execute the following switches ​during the configure process.+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 bash src directory. In my case. “cd /scratch/bash-3.2/”+Change to your SED src directory. In my case. “cd /scratch/sed-4.1.5/”
  
-Then execute the following command.. ./​configure ​–enable-static-link –without-bash-malloc+Then execute the following command.. ./​configure ​
  
 Once the configure process is complete, and provided there were no errors. Execute the following commands. Once the configure process is complete, and provided there were no errors. Execute the following commands.
Line 15: Line 15:
 Then Then
  
-make+make CC="​gcc -static"​
  
-Again, provided there were no errors during the build process you should be left with a file in /​scratch/​bash-3.2/ named “bash”.+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/bash-3.2/bash ( Fully path it to make sure it doesn'​t pick up on anything else. )+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 ​bash-3.2]# file /scratch/bash-3.2/bash /scratch/bash-3.2/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, statically linked, not stripped+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. 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/bash-3.2/bash: 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!+/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!
  

QR Code
QR Code appnotes:sed_-_build_instructions (generated for current page)