Date: Tue, 11 May 1999 09:09:56 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Daniel Barker cc: djgpp AT delorie DOT com Subject: Re: Failed compilation of GCC 2.8.1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 10 May 1999, Daniel Barker wrote: > The directory into which I had unzipped the source > distribution was "/unzipped/", which is not my main DJGPP directory. This might be a bad idea. In general, DJGPP packages should be unzipped from the main DJGPP directory; ports of GNU packages install their sources in the gnu/ subdirectory. Some packages might rely on being installed in %DJDIR%/gnu, although I don't know whether GCC relies on that. Anyway, there should be no reason for you to avoid unzipping the sources where they belong, since the source distribution doesn't overwrite any files from your binary installation. > If there is a good reason why GCOV is left out of the binary distribution, > perhaps because it does not work with DJGPP, I would be grateful for any > information on that as well. `gcov' requires special code be emitted by a compiler into the program. I don't remember if that part of the compiler is operational in the DJGPP port. If you do succeed to port `gcov', please consider posting the necessary changes here. > c:/local/djgpp/bin/ld.exe: cc1: warning: .text: line number overflow: > 0x13b75 > 0xffff You are hitting the limitation of the COFF object file format: the total number of source lines in a program must be less than 65535, otherwise the linker cannot write the debug info. The usual work- around is to add `CFLAGS=-O2' to the Make command lines you are invoking during the build (you could also set CFLAGS in the environment to get the same effect). This value of CFLAGS prevents gcc from putting debug info in the first place, and also makes the code smaller and faster due to optimizations. > Load error: can't switch mode This usually means that the Windows DPMI server has run out of protected-mode selectors, and thus gcc cannot switch into protected mode. If this happens after a lot of make/gcc invocations, it is a manifestation of the known bug in Windows 9X/NT whereby each nested DPMI program invocation loses selectors. Closing the DOS box and opening a new one will usually solve the problem.