Back to wiki

RCS History

/ TOP / how-it-works.mdwn

Differences for revision 1.3 from 1.2


--- /how-it-works.mdwn	2008/01/23 03:18:24	1.2
+++ /how-it-works.mdwn	2010/02/26 13:38:36	1.3
@@ -58,7 +58,7 @@
 
     $ pcc -g -O -I/usr/local/include -D_DEBUG -Wl,-r/usr/local/lib prog.c
 
-The first option is _-g_ which instructs the compilation process to compile with debugging information.  This options is not needed by the pre-processor, but is used by the compiler, assembler and sometimes the linker to put debugging information in the executable.  This information can be used by a symbolic debugger.
+The first option is _-g_ which instructs the compilation process to compile with debugging information.  This options is not needed by the pre-processor, but is used by the compiler, assembler and sometimes the linker [resume writing services](http://cvresumewritingservices.org/) to put debugging information in the executable.  This information can be used by a symbolic debugger.
 
 The second option is _-O_ which enables compiler optimizations.  It is only used by the compiler and is not needed by the pre-processor, assembler nor linker.
 
@@ -68,7 +68,7 @@
 
 The fifth option is _-Wl,-r/usr/local/lib_ which instructs the linker to record this directory in the executable for use by the dynamic linker.  It's only used by the linker and is not needed by the pre-processor, compiler nor assembler.
 
-From this analysis, we can appreciate that the steps required to achieve compilation and how all those command-line arguments work together to generate a binary executable.
+From this analysis, we can appreciate that the steps required to achieve compilation [custom writing](http://custom-essay-writing-service.org/index.php) and how all those command-line arguments work together to generate a binary executable.
 
 If _pcc_ ever has a problem generating a binary executable, then the problem must be attributed to one of these steps of the build process.
 

Powered by rcshistory.cgi 0.3