From fnaumann@mail.cs.uni-magdeburg.de Fri Sep 24 01:58:11 2004 From: Henk Robbers To: mint@fishpool.com Subject: Re: [MiNT] Current Binaries Date: Fri, 24 Sep 2004 02:25:40 +0200 User-Agent: KMail/1.5.1 References: <41518310.9050502@lutece.net> <1095969673.9066.5.camel@pikachu.atari-source.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409240225.41231.h.robbers@chello.nl> Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: h.robbers@chello.nl Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel On Thursday 23 September 2004 22:05, Frank Naumann wrote: > Hello! > > > I have no problem doing this. > > That's nice to hear :-) > > > to get this done on the server itself ;-) Just have to make sure > > mintlib, gemlib and the other tools are up to date on the cross > > distribution. > > You can also cross compile mintlib/gemlib and use them for compiling > freemint & tools. If the interaction between XaAES and the kernel is well established and doesnt change, there is no need to make a release of XaAES binary together with a new kernel binary. This way xaaes.atari.org can be kept very much alive. MiNT/XaAES.km runs pretty efficient on a TT. I dont even consider trying to use gcc on my TT, if at all possible. So I am very dependent on binary releases, and I think I am not the only one. -- Groeten; Regards. Henk Robbers. mailto:h.robbers@chello.nl http://members.ams.chello.nl/h.robbers/Home.html Interactive disassembler: TT-Digger; http://digger.atari.org A Home Cooked teXt editor: AHCX