From mint-bounce@lists.fishpool.fi Sun Sep 17 03:19:54 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=i0pMOX6NSxUgg6xXwcbE2IfoViNp0Vynp3avSLX44vHZ/QLHnDq2/+AUT8OUlQRK5QLkp8O5KDKzOpwZhFJptJNZ19Myc5ab0Er39iwN1I0qFZQKzdHsY7ScBztINCb57XL0kvsbUJmylfwd1ovktTGVQrcpY4T+BcHfFoAhcPw= From: MiKRO Organization: Mystic Bytes To: mint@fishpool.com Subject: [MiNT] glibc for m68k/mint? Date: Sun, 17 Sep 2006 03:06:23 +0200 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609170306.23477.miro.kropacek@gmail.com> 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: 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: 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 :)