{"id":142,"date":"2020-09-27T07:29:20","date_gmt":"2020-09-27T07:29:20","guid":{"rendered":"https:\/\/smedley.id.au\/os2ports_wp\/?page_id=142"},"modified":"2020-09-27T09:17:00","modified_gmt":"2020-09-27T09:17:00","slug":"gcc-v4-3-x","status":"publish","type":"page","link":"https:\/\/os2ports.smedley.id.au\/?page_id=142","title":{"rendered":"GCC v4.3.x"},"content":{"rendered":"\n

Mainly due to the fact that GCC 3.3.5 (which is what is currently used by kLibc) is becoming too old to build the latest Mozilla trunk code, I started working on building a newer version of GCC.<\/p>\n\n\n\n

I’ve started with v3.4.6 – as the thought was that the amount of changed between 3.3.5 and 3.4.6 would be comparatively small compared with aiming for the ‘latest’ GCC (currently 4.3.3).  I now have builds of 3.4.6, 4.0.4 and 4.3.3; The current binary of GCC 4.3.3 has been used to build several projects successfully – ie rsync, Apache2, MySQL, Firefox 3.0-cvs, Ghostscript, ffmpeg amongst others<\/p>\n\n\n\n

 Known Issues with the current 4.3.3 release (2009-2-24)<\/p>\n\n\n\n

– link warning when using -Zomf – emxomf will require updating to deal with the new stabs types, but according to Knut, these warnings can be safely ignored, and only affect debugging<\/p>\n\n\n\n

Updates since original build – the date in brackets reflects the first build that contained the fix<\/p>\n\n\n\n