|  | @@ -13,11 +13,11 @@ Install M4 by running the following commands:
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  <para>
 | 
	
		
			
				|  |  |  If the base system is running a 2.0 kernel and the Glibc version is
 | 
	
		
			
				|  |  | -2.1 then a user will most likely get problems executing M4 in the
 | 
	
		
			
				|  |  | +2.1 then you will most likely get problems executing M4 in the
 | 
	
		
			
				|  |  |  chroot'ed environment due to incompatibilities between the M4 program,
 | 
	
		
			
				|  |  | -Glibc-2.1 and the running 2.0 kernel. If he has problems executing the 
 | 
	
		
			
				|  |  | -m4 program in the chroot'ed environment (for example when he installs 
 | 
	
		
			
				|  |  | -the autoconf and automake packages) he'll have to exit the chroot'ed 
 | 
	
		
			
				|  |  | +Glibc-2.1 and the running 2.0 kernel. If you have problems executing the 
 | 
	
		
			
				|  |  | +m4 program in the chroot'ed environment (for example when you install 
 | 
	
		
			
				|  |  | +the autoconf and automake packages) you'll have to exit the chroot'ed 
 | 
	
		
			
				|  |  |  environment and compile M4 statically. This way the binary is linked 
 | 
	
		
			
				|  |  |  against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as 
 | 
	
		
			
				|  |  |  well on a decent system. Kernel 2.0 and Glibc-2.1 don't mix very well) 
 |