Date: Sun, 17 Dec 2000 15:40:10 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp-workers AT delorie DOT com Subject: Re: gcc-2.95.* for DJGPP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Sun, 17 Dec 2000, Andris Pavenis wrote: > The problems I got was linked with libio. For a rather long time > (before switching to libstdc++-v3) I had problems building development > versions for DJGPP (mostly as cross-compiler) due to broken libio: > - the prototypes of rather many function doesn't fit with > their definitions > This shows only if types of off_t and fpos_t are different (eg. signed > and unsigned ints) and it doesn't appear for example under Linux > and maybe some other systems. > > Now this breakage is taken to gcc-2.95 branch. I workarounded it by > patching some files in libio. This problem really bugs me. I couldn't make any sense out of the problems, when Andris posted the relevant error messages and source fragments several weeks ago. Could someone please look into this and see why doesn't libio compile cleanly? I'm worried that more of such problems will creep into libstdc++ if we don't fix them and send patches to maintainers.