From mint-bounce@lists.fishpool.fi Sun Sep 17 12:05:33 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Sun, 17 Sep 2006 11:56:42 +0200 (CEST) From: Frank Naumann X-X-Sender: fnaumann@wh58-508.st.uni-magdeburg.de To: mint@fishpool.com Subject: Re: [MiNT] glibc for m68k/mint? In-Reply-To: <200609170306.23477.miro.kropacek@gmail.com> Message-ID: References: <200609170306.23477.miro.kropacek@gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-365521517-1158487002=:417" X-Scan-Signature: 27004fcae819a2059f0002d3dbe0a950 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: fnaumann@boerde.de 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=-0.9 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-365521517-1158487002=:417 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hello! > born from the beginning... what was the reason to not use/port glibc from > linux/unix world? You need to move all of the ATARI compatibility stuff from mintlib to=20 glibc. Thus is much easier to move the things you like to have in mintlib= =20 from glibc to mintlib ... Or you loose the ability to run gcc compiled programs under TOS / MagiC=20 at all. At the moment you can use the gcc to develop programs for TOS /=20 MagiC too (if you keep some points in mind). You also need to modify all=20 existing AES programs, that use the gcc, I'm sure. > 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... That's not true. Mostly all of the newer things are taken from glibc (and= =20 eventually adapted for the ATARI environment). > I ask because "our" libc development seems to be a little inactive Is there anything that you are missing? At the moment the mintlib is very= =20 stable and compatible enough for mostly al=C3l unix programs (for the libc= =20 dependency). Regards, Frank -- ATARI FALCON 060 // MILAN 060 -------------------------------- http://sparemint.atariforge.net/ e-Mail: fnaumann@freemint.de --0-365521517-1158487002=:417--