Message-ID: <20010111124713.15142.qmail@lauras.lt> From: "Laurynas Biveinis" Date: Thu, 11 Jan 2001 14:47:13 +0200 To: djgpp-workers AT delorie DOT com Subject: Re: RFC: libstdc++-v3 port Mail-Followup-To: djgpp-workers AT delorie DOT com References: <20010111120100 DOT 572 DOT qmail AT lauras DOT lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eliz@is.elta.co.il on Thu, Jan 11, 2001 at 02:08:01PM +0200 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, Jan 11, 2001 at 02:08:01PM +0200, Eli Zaretskii wrote: > On Thu, 11 Jan 2001, Laurynas Biveinis wrote: > > > Below is preliminary port of libstdc++-v3 to DJGPP. There are still > > quite a few rough edges with configure, libtool, etc., but I'd like > > to submit this part before GCC 3.0 branch. Any comments? > > Could you possibly say a few words about why each patch is required? There is only one non-trivial thing (from libstdc++ point of view): libstdc++-v3 ctype support. Libstdc++ wants to have efficient implementation of it, so it asks for libc details about internal is*(), tolower(), toupper() implementation. So new headers ctype_base.h, ctype_inline.h and ctype_noninline.h teach about __dj_type_cflags[] and other arrays and how to use them. Patch to acinclude.m4 checks if system's is really a DJGPP one before using the abovementioned code. Everything else are just infrastructure bits and stubs for things like thread safety. Laurynas