Date: Wed, 14 Jun 2000 17:24:03 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp-workers AT delorie DOT com Subject: Re: Warning patch for exceptn.S In-Reply-To: <3947AA3B.21327.5284DC@localhost> 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 Wed, 14 Jun 2000 pavenis AT lanet DOT lv wrote: > > Is there perhaps some preprocessor magic that should help us out? I'm > > thinking about keeping the old code for older Binutils, the new one for > > v2.10 and later, and having some #ifdef or assembly-level directive to > > choose between them. Is this possible? > > So we should detect version of GNU assembler somewhere. That's easy to do in makefile.def, before starting the library build: GAS_VERSION := $(shell $(CROSS_GAS) --version | sed -e 'remove-junk') (here "remove-junk" is some script that removes everything but the version number). CROSS_GAS will need to be added to expand either to "as" or to "i586-pc-msdosdjgpp-as", depending on whether this is a native or a cross build. > Maybe we could also remove -Werror when compiling .S files. So we'll > get warnings with current sources but at least no bigger problems. That would be the fallback, yes. But some people become nervous when they see warnings during library build, so if this can be avoided, I think we should. > PS. I put my build of DJGPP binary archive of binutils-2.10 release > candidate 3 at http://www.lanet.lv/~pavenis/djgpp/bnu210rc3.zip > if You are interested to do some testing and don't want to build it > Yourself. As usually it's built under Linux (by cross-compiling) Thanks.