From owner-mint@fishpool.com Thu Apr 17 17:04:41 2003 To: mint@fishpool.com Subject: Re: [MiNT] line-endings and MiNT-Lib? Message-ID: <1050591725.3e9ec1ed44cca@imp.free.fr> Date: Thu, 17 Apr 2003 17:02:05 +0200 (CEST) From: Xavier Joubert References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.6 X-Originating-IP: 212.234.144.141 Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: xavier.joubert@free.fr Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Hi Frank, En réponse à Frank Naumann : > Some tools (I remember gnupg and rpm) don't work correctly if the > stdin/stdout/stderr isn't initialized statically (this is why the > previous > dynamic initialiazion isn't fail safe in every case). Beside from that > it's a little bit mysterious as the static initialization should be > exatcly the same as the dynamic (at least I can't see any difference). But the difference is here nevertheless. Under TOS, static initialization make *printf output LF only while it should output CRLF. > > Does that mean that for the time being we are stuck with the ugly > (and > > error-prone) search-and-replace solution? > I don't understand what do you mean with that. He means that he needs to replace every single '\n' in source code by '\r\n' for the program to be useable under TOS. I would vote for the removal of static initialization (ie application of Patrice's patch). Then, if we have trouble with some software under MiNT, we will need to find a way to fix this without breaking TOS support. My 2 euro-cents, Xavier