From mint-bounce@lists.fishpool.fi Sun Sep 17 14:05:33 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:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=PwhUhKf9c0aVM2nM+MV43qWzkmwNm+wAysGkQUbo1E1HPwjCjc8yk7ewH02+2nzCwZ0jHuWpKikaoY8q/fnCAELOKI8mv2kGMZzFVQ5Y8UJjSQgfnA7Joyxl2aT4lQrXnFdXk7eo2KAfrI6mPO7qiFudSEffHeaBuYtten+kqOQ= From: MiKRO Organization: Mystic Bytes To: mint@lists.fishpool.fi Subject: Re: [MiNT] glibc for m68k/mint? Date: Sun, 17 Sep 2006 13:55:33 +0200 User-Agent: KMail/1.9.1 References: <200609170306.23477.miro.kropacek@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Message-Id: <200609171355.33229.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: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id k8HC5X92022985 > You need to move all of the ATARI compatibility stuff from mintlib to > glibc. Thus is much easier to move the things you like to have in mintlib > from glibc to mintlib ... > no doubt. i just asked because according to glibc docs this library should be extremely portable. > Or you loose the ability to run gcc compiled programs under TOS / MagiC > at all. At the moment you can use the gcc to develop programs for TOS / > MagiC too (if you keep some points in mind). You also need to modify all > existing AES programs, that use the gcc, I'm sure. > oops, this is a problem then, we can't do this for sure. let's add the reply about ram-hungry programs and... no way. > Is there anything that you are missing? At the moment the mintlib is very > stable and compatible enough for mostly alÃl unix programs (for the libc > dependency). > no no, i didn't ask because i'm missing something... i was just curious since i see from time to time glibc updated version XY, new features, bugfixes etc and mintlib development is still silent. so maybe we have 100% bugfixed libc who knows ;)