published by tom on Tue, 04/05/2016 - 17:48    
  
  
      
  
  
 
        
    
      
            published by tom on Mon, 05/09/2016 - 15:12    
  
  
      
  
  
 
        
    
      
            published by tom on Sat, 04/02/2016 - 21:09    
  
  
      
  
  
 
        
    
      
            published by tom on Wed, 12/25/2013 - 18:55    
  
  
    Update: For SFEgcc 4.8 SFE still uses the LINK_LIBGCC_SPEC to really load the very own gcc runtime if ever possible (20150515)
Thanks to some notes from a well known compiler guru, I got aware of an important but unfortunatly not default setting in the gcc compiler.
 
      
  
  
 
        
    
      
            published by tom on Wed, 12/25/2013 - 18:19    
  
  
    Just wanted to drop a note:
 
      
  
  
 
        
    
      
            published by tom on Fri, 06/21/2013 - 20:19    
  
  
      
  
  
 
        
    
      
            published by tom on Fri, 02/22/2013 - 16:17    
  
  
      
  
  
 
        
    
      
            published by tom on Thu, 06/07/2012 - 12:03    
  
  
      
  
  
 
        
    
      
            published by tom on Mon, 04/02/2012 - 17:32    
  
  
    Quick and condensed my thoughts about how a gcc should be compiled to plan forward for future upgrades and safety measure to not interfere with other gcc runtime libraries you might have.
A distribution does keep the door open for future changes without breaking old binaries if following the concept from below.
 
      
  
  
 
        
    
      
            published by tom on Sun, 09/25/2011 - 02:20    
  
  
    Update: I put together a condensed set of notes for a distribution to make up a nice gcc configuration here: http://tom.blog.in-ulm.de/gcc_cookbook_for_a_distribution
Update: As of end of December 2011 the new setup for gcc described below has been released from experimental a long time ago - and no known bugs yet.
Unfortunatly the OS-Distro provided gcc-4 series compilers still do not follow this approach.