Mail Archives: djgpp-workers/1999/11/07/08:00:19
Andris said:
> On 6 Nov 99, at 15:05, Martin Str|mberg wrote:
> Just joke
>
> cd c:\djgpp
> rm -vf @manifest/bnu281s.mft
Right! He-he!
> > 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
Ok. There isn't anything that can make the debugging work? I don't
_think_ I'll need that but later on I'll surely will (Murphy's law...).
> One more question: did You apply patch to fix problem with local
> labels I mentioned?
No, it's a pure tar-ball from a gnu mirror. Where can I get it? I
don't really need it - right now I don't care if the binaries are
bloated as long as they function.
> If You want, I can make available some of my builds of recent binutils
> snapshots
Do they include ELF as a target? (Don't tell anyone but I'm examining
the possibility to move DJGPP to ELF.)
Oldfield, Turbular Bells III,
MartinS
- Raw text -