|  | @@ -7,18 +7,16 @@ our toolchain. We'll adjust it so that it will link any newly compiled program
 | 
	
		
			
				|  |  |  against the new C libraries. Basically, this is the reverse of what we did
 | 
	
		
			
				|  |  |  in the "Locking in" stage in the beginning of the previous chapter.</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<para>The first thing to do is to adjust the linker scripts. For this we
 | 
	
		
			
				|  |  | -retained the source and build directories from the second pass over Binutils.
 | 
	
		
			
				|  |  | -Install the adjusted linker scripts by running the following from within the
 | 
	
		
			
				|  |  | +<para>The first thing to do is to adjust the linker. For this we retained the
 | 
	
		
			
				|  |  | +source and build directories from the second pass over Binutils. Install the
 | 
	
		
			
				|  |  | +adjusted linker by running the following from within the
 | 
	
		
			
				|  |  |  <filename class="directory">binutils-build</filename> directory:</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<para><screen><userinput>make -C ld install-data-local</userinput></screen></para>
 | 
	
		
			
				|  |  | +<para><screen><userinput>make -C ld install</userinput></screen></para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -<para>The linker scripts now contain
 | 
	
		
			
				|  |  | -no mention of <filename class="directory">/tools/lib</filename> anymore.
 | 
	
		
			
				|  |  | -From now on every compiled program will link <emphasis>only</emphasis>
 | 
	
		
			
				|  |  | -against the libraries in <filename>/usr/lib</filename> and
 | 
	
		
			
				|  |  | -<filename>/lib</filename>.</para>
 | 
	
		
			
				|  |  | +<para>From now on every compiled program will link <emphasis>only</emphasis>
 | 
	
		
			
				|  |  | +against the libraries in <filename>/usr/lib</filename> and <filename>/lib
 | 
	
		
			
				|  |  | +</filename>.</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <para>You can now remove the Binutils source and build directories.</para>
 | 
	
		
			
				|  |  |  
 | 
	
	
		
			
				|  | @@ -34,14 +32,8 @@ mv newspecfile $SPECFILE
 | 
	
		
			
				|  |  |  unset SPECFILE</userinput></screen></para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <para>Again, cutting and pasting the above is recommended. And just like
 | 
	
		
			
				|  |  | -before, it is a good idea to check the linker scripts and the specs file to
 | 
	
		
			
				|  |  | -ensure the intended changes were actually made.</para>
 | 
	
		
			
				|  |  | -
 | 
	
		
			
				|  |  | -<para>Note that the linker scripts will still contain a reference to
 | 
	
		
			
				|  |  | -<filename class="directory">/tools/i686-pc-linux-gnu/lib</filename>. This
 | 
	
		
			
				|  |  | -is unavoidable, but luckily does not present a problem. There are no
 | 
	
		
			
				|  |  | -libraries in that location as all the temporary tools libraries are
 | 
	
		
			
				|  |  | -located in <filename class="directory">/tools/lib</filename>.</para>
 | 
	
		
			
				|  |  | +before, it is a good idea to check the specs file to ensure the intended
 | 
	
		
			
				|  |  | +changes were actually made.</para>
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <caution><para>It is imperative at this point to stop and ensure that the
 | 
	
		
			
				|  |  |  basic functionality of the adjusted toolchain is working as expected. We are
 |