From mint-bounce@lists.fishpool.fi Sun Sep 17 05:31:00 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] glibc for m68k/mint? From: Mark Duckworth To: MiKRO Cc: mint@fishpool.com In-Reply-To: <200609170306.23477.miro.kropacek@gmail.com> References: <200609170306.23477.miro.kropacek@gmail.com> Content-Type: text/plain Date: Sat, 16 Sep 2006 23:25:55 -0400 Message-Id: <1158463555.6524.30.camel@evil.atari-source.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Glibc depends heavily upon the linux kernel as far as I know. Without modern kernel interfaces, no modern libc. We need virtual memory. I thought you were working on that :-P Thanks, Mark On Sun, 2006-09-17 at 03:06 +0200, MiKRO wrote: > Hello, > > I apologize for maybe such stupid question but I haven't been by mintlib's > born from the beginning... what was the reason to not use/port glibc from > linux/unix world? From my point of view it seems a large parts were written > from scratch by former mint/mintlib maintainers and I see no reason for > this... > > I ask because "our" libc development seems to be a little inactive and maybe > it would be a good idea to think about something like porting glibc to mint > and to be compatible with the rest of the world... (ok now it's that > compatibility also high but you know what I want to say :) > >