From mint-bounce@lists.fishpool.fi Fri Jan 1 18:12:52 2010 Message-ID: <4B3E80FE.1070107@freesbee.fr> Date: Sat, 02 Jan 2010 00:10:54 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] [Mint-cvs] [FreeMiNT CVS] freemint/sys/sockets/inet4 References: <201001011533.o01FXxwV032211@mail.sparemint.org> <1262366629.16683.1686.camel@jetpack.demon.co.uk> <4B3E336F.5010502@atari.org> <4B3E349B.9030100@freesbee.fr> <4B3E3C25.1000602@atari-source.org> <4B3E486B.2010507@atari-source.org> <4B3E5FD9.9040508@atari-source.org> <4B3E71C5.9070803@online.no> <4B3E7ADB.6050506@atari.org> In-Reply-To: <4B3E7ADB.6050506@atari.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100101-0, 01/01/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o01NCpvK007651 Odd Skancke wrote: > My main developmentenvironment is GCC 4.4.2/KDE > on Fedora. On this beast, it takes 16 seconds to build the kernel from > distclean. I dont want to loose that luxury :) This is the voice of reason. It is a fact that modern versions of GCC require strong hardware. It would be a nonsense to run it on older Atari machines, since the *exact* same result can be achieved with a cross-GCC running on a modern computer. There are a lot of people that hate cross-compilers. Fortunately, it is not the case of everyone. I hope the developers of games on GameBoy or cell phones don't run GCC on that hardware :-) Be sure that bytes are clean entities. The bytes produced by GCC running on Atari hardware and the ones produced on a cross-GCC running on Windows or Linux are exactly the same. One to one. They don't smell bad. For me, the choice has been made for a long time. I use my main modern computer to write and compile programs, then I can run them on my favourite hardware (or emulators). > vice versa, it will be very difficult keeping this under control via > #ifdefs within a single source tree. And I hate these kinds of #ifdefs :-) What are those huge differences ? GCC 4.x is more picky than earlier versions, thus the code has sometimes to be cleaned up. But the resulting code should work perfectly on older compilers. Or except extremely specific cases. Am I wrong ? -- Vincent Rivière