From mint-bounce@lists.fishpool.fi Wed Mar 4 07:41:13 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=s0IDoTlTrbZxFPYIq020u26CfImqibHXgxs7Uq2L3II=; b=J/8MzgDwj95XXN1hzsoSINJQSKjz3ucpHjqsRTGK3BheBElbaQgBUkYEfzV/5HYq8S LQXLXgjsF+gM9y9pUQwylH+WbUUiRgibKNH95uJBrlyYSHTuODICm1+DC8WoVS0EMgD7 NjJTD7UmEQPN3GPpDXHgQaR628dY9IMppQBg4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wJRY5Odb3s9kxemj+gTvxOy9V4PSyKGoEGRvX4DIJK0u0WsLmbJrw/NQyAgorkejvT jJZwxVD5Nlrm42JyRMd1sus/9M/rl8UaKUBm7yjZbGrsKAZtZfQtrZFVd/pmMURupEeB vejNk6WRXppSmtuezS63Hk5WVj03tkfN6LE9A= MIME-Version: 1.0 In-Reply-To: <1236166911.31691.43.camel@petr> References: <49AE5A7F.8020504@freesbee.fr> <1236164700.29646.19.camel@jetpack.demon.co.uk> <1236166911.31691.43.camel@petr> Date: Wed, 4 Mar 2009 13:38:53 +0100 Message-ID: Subject: Re: [MiNT] MPFR progress..... From: Miro Kropacek To: Petr Stehlik Cc: mint@lists.fishpool.fi Content-Type: multipart/alternative; boundary=000e0cd250aaa1d03104644a5567 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --000e0cd250aaa1d03104644a5567 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit > > yes, please, mint/lib(c) should provide TOS compatibility until FreeMiNT > is the primary OS on majority of Atari machines ;-) I don't know. Considering the fact most of portable software (this is what we're talking about, right?) depends on filesystem with long names, a lot of memory, fast CPU etc -- how many apps/games would you like to run on anything other than CT60/Aranym? And since there's always "dummy proof" EasyMiNT, everyone is free to install the OS even just for running ported stuff. Not big sacrifice I think. Plus, let's review the recent mint list issues, which started this discussion -- everything was about gcc, ssh, binutils, coreutils, ... packages. Nothing you'd like to use on TOS. Other side is native Atari development -- in case I'm programming normal GUI application I'd be certainly happy to have it runnable on plain TOS / older Atari machines. In this case maybe current mintlib would be sufficient (+ the Vincent's work on ELF obj format I'd say perfect). -- MiKRO / Mystic Bytes http://mikro.atari.org --000e0cd250aaa1d03104644a5567 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
yes, please, mint/lib(c) should provide TOS compatibility until F= reeMiNT
is the primary OS on majority of Atari machines ;-)
I don&= #39;t know. Considering the fact most of portable software (this is what we= 're talking about, right?) depends on filesystem with long names, a lot= of memory, fast CPU etc -- how many apps/games would you like to run on an= ything other than CT60/Aranym? And since there's always "dummy pro= of" EasyMiNT, everyone is free to install the OS even just for running= ported stuff. Not big sacrifice I think.

Plus, let's review the recent mint list issues, which started this = discussion -- everything was about gcc, ssh, binutils, coreutils, ... packa= ges. Nothing you'd like to use on TOS.

Other side is native Atar= i development -- in case I'm programming normal GUI application I'd= be certainly happy to have it runnable on plain TOS / older Atari machines= . In this case maybe current mintlib would be sufficient (+ the Vincent'= ;s work on ELF obj format I'd say perfect).



--
MiKRO / Mystic Bytes
http://mikro.atari.org
--000e0cd250aaa1d03104644a5567--