From: pavenis AT lanet DOT lv To: "Norberto Alfredo Bensa" , djgpp-workers AT delorie DOT com Date: Mon, 28 May 2001 13:06:21 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: gcc 2.95.3 can't built itself? Message-ID: <3B124D4D.27159.ABA924@localhost> In-reply-to: <02de01c0e748$e9bfda20$0100a8c0@fibertel.com.ar> X-mailer: Pegasus Mail for Win32 (v3.12c) 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 28 May 2001, at 4:36, Norberto Alfredo Bensa wrote: > > > > Haven't met anything similar however I used binutils-2.9.1 (not 2.11) to > > build gcc-2.95.3 for DJGPP (otherwise -mno-bnu210 would be useless > > as I should get gcc binaries incompatible with binutils 2.[89].*) > > > > One more difference is that I build gcc-2.95.3 for DJGPP under Linux > > (native building is less tested this time but it worked for me at least > > once) > > > > I suggest to rerun stage3 after adding -save-temps to CFLAGS and > > inspect assembler output near failure > > > > Ok, how do I rerun stage3? build.bat does the whole process again... > Then look what's inside build.bat ... (it simply calls bash script djbuild1.sh with corresponding parameters) Andris