From: pavenis AT lanet DOT lv Message-ID: To: Martin Str|mberg , djgpp-workers AT delorie DOT com Date: Sat, 6 Nov 1999 17:28:20 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: binutils building problem In-reply-to: <199911061405.PAA25892@father.ludd.luth.se> References: from Andris Pavenis at "Nov 4, 99 10:10:26 am" X-mailer: Pegasus Mail for Win32 (v3.12a) Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 6 Nov 99, at 15:05, Martin Str|mberg wrote: > Hello Andris. > > > I tried to build binutils 2.8.1 from the sources in bnu281s.zip from a > simtel.net mirror. > > First problem: configure.bat have probelms applying the patches: > > "bash$ cd hackery/binutils2.81.another_one/gnu/binutl-2.81/ > bash$ ./configure.bat > Applying DJGPP specific patches ... > can't find file to patch at input line 3 > Perhaps you should have used the -p or --strip option? > The text leading up to this was: > -------------------------- > |--- binutils/nlmconv.c~ Wed Apr 30 18:59:12 1997 > |+++ binutils/nlmconv.c Sat Jun 28 21:39:44 1997 > -------------------------- > File to patch: 1111 > Skip this patch? [y] > Skipping patch. > 3 out of 3 hunks ignored" > > (I entered 1111 and a lot of C-cs to stop it). > > Totally confused I let it rest for a day or so, then I ran > "./configure.bat |tee configure.bat.log" to save the result for > mailing to you. Now it worked! > > Something is wrong somewhere. Do you have any ideas? Perhaps this > should be asked on DJGPP-WORKERS? If you think so, please forward this > mail. > Once I tried to build binutils-2.8.1 for DJGPP due to fix for problem with local labels (GAS put them into object file). Building binutils-2.8.1 were almost nightmare but finally I suceeded. After that I moved to binutils-2.9.1 and it builds much more easy. I'm using binutils-2.9.1 for most things (for example gcc built using recent binutils snapshots gives executables that are not usable with earlier versions, otherwise perhaps there is no problems) > > Second problem: make fails (I'm running it in emacs): > > "gcc -c -D_GNU_SOURCE -I. -I. -I./../include -O2 -fno-omit-frame-pointer i386aout.c > if [ -n "" ]; then \ > gcc -c -D_GNU_SOURCE -I. -I. -I./../include -O2 -fno-omit-frame-pointer aout32.c -o pic/aout32.o; \ > else true; fi > gcc -c -D_GNU_SOURCE -I. -I. -I./../include -O2 -fno-omit-frame-pointer aout32.c > make.exe[1]: *** No rule to make target `i386msdos.c', needed by `i386msdos.o'. Stop. > make.exe[1]: Leaving directory `f:/hackery/binutils2.81/gnu/binutl-2.81/bfd' > make.exe: *** [all-bfd] Error 2 > > Compilation exited abnormally with code 2 at Sat Nov 6 14:40:18 > " > > What should I do now? > Just joke cd c:\djgpp rm -vf @manifest/bnu281s.mft > > Third problem: strange link message while building binutils 2.9.1: > Well, there's nothing stopping me now, I thought, let's go for > binutils 2.9.1. It seems to make correctly, but I get these strange > messages from the make process (the first two): > > "gcc -g -o size size.o bucomm.o version.o filemode.o ../bfd/.libs/libbfd.a ../libiberty/libiberty.a > f:/djgpp/bin/ld.exe: size: warning: .text: line number overflow: 0x16f8b > 0xffff" > > and > > "gcc -g -o objdump objdump.o prdbg.o rddbg.o debug.o stabs.o ieee.o rdcoff.o bucomm.o version.o filemode.o ../opcodes/.libs/libopcodes.a ../bfd/.libs/libbfd.a ../libiberty/libiberty.a > f:/djgpp/bin/ld.exe: objdump: warning: .text: line number overflow: 0x1b314 > 0xffff" > > There are a total of 16 of such warnings. Are they be taken as > "comiplation failed" or are they harmless? What do they mean (if you > know)? > There will be problems with debug info (COFF limitations). Unless You are going to debug binutils You can ignore them. Or specify CFLAGS=-O2 One more question: did You apply patch to fix problem with local labels I mentioned? If You want, I can make available some of my builds of recent binutils snapshots Andris