From mint-bounce@lists.fishpool.fi  Mon Mar  2 06:14:09 2009
X-Virus-Scanned: amavisd-new at demon.co.uk
Subject: Re: [MiNT] Gcc 3.3.6 v 4.0.1
From: Alan Hourihane <alanh@fairlite.co.uk>
To: Vincent =?ISO-8859-1?Q?Rivi=E8re?= <vincent.riviere@freesbee.fr>
Cc: mint@lists.fishpool.fi
In-Reply-To: <49ABB658.8050702@freesbee.fr>
References: <20090225103817.swnyw26m0wgk8osc@pop.freeola.net>
	 <373EB9E0-576D-4D59-B0A9-829AD39EB08F@gmail.com>
	 <c6533ef60902250323y7091ce02mbb09a78c9bf3c86a@mail.gmail.com>
	 <49A535ED.6000008@freesbee.fr> <49A56B1A.9050304@atari-source.org>
	 <49A5C597.9030003@freesbee.fr>  <49A65413.2020403@freesbee.fr>
	 <1235640237.13634.231.camel@jetpack.demon.co.uk>
	 <49AB214A.6020802@freesbee.fr>
	 <1235954690.25551.96.camel@jetpack.demon.co.uk>
	 <49ABABC3.2030509@freesbee.fr> <1235988212.6867.3.camel@petr>
	 <49ABB658.8050702@freesbee.fr>
Content-Type: text/plain; charset=UTF-8
Date: Mon, 02 Mar 2009 11:10:21 +0000
Message-Id: <1235992221.8006.11.camel@jetpack.demon.co.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: alanh@fairlite.co.uk
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n22BE31E021735

On Mon, 2009-03-02 at 11:35 +0100, Vincent Rivière wrote:
> Petr Stehlik wrote:
> > Sounds like MiNTLib should become a patch to glibc - then tracking the
> > changes by GNU would be easier, perhaps :)
> 
> Yes, that is the definitive solution.
> But the glibc is huge, I heard it can be difficult to port it to 
> something other than Linux. The situation may be better now.

If we want to run this on 68000 machines with 4MB of RAM, then I think
glibc is not an option.

> However, there are alternatives to glibc, for example Newlib, uclibc, 
> dietlibc...

Yes. newlib I think is the best choice here.

> Newlib is a very good choice: it has been designed to be portable. It is 
> required to implement less than 10 "system calls" in order to get it 
> work on a new system. I even managed to let it work on plain TOS as a 
> replacement for the MiNTLib ;-) (be quiet: it was only a very incomplete 
> test).
> 
> However, Newlib has less functionality than glibc (for example, that 
> damn obstream stuff is not present). For information, Cygwin uses 
> Newlib, not glibc. The good news is that most makefiles of GNU software 
> are aware of Newlib, it can ease porting them.
> 
> Unfortunately, I guess the MiNTLib has been heavily patched from the 
> original sources, so it could be extremely difficult to port the added 
> functionalities to another libc. But I think it is the only way to get 
> the new functionalities and bugfixes from the community. I don't think 
> the MiNTLib could survive without this.

I agree we need to look to some integration with an existing project to
reap the benefits.

Alan.


