X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Received:	by 10.13.246.131 with SMTP id g125mr15221418ywf.32.1434072922387;
	Thu, 11 Jun 2015 18:35:22 -0700 (PDT)
X-Received:	by 10.140.96.137 with SMTP id k9mr195716qge.10.1434072922367; Thu,
	11 Jun 2015 18:35:22 -0700 (PDT)
Newsgroups:	comp.os.msdos.djgpp
Date:	Thu, 11 Jun 2015 18:35:22 -0700 (PDT)
In-Reply-To:	<557A1996.7040008@gmail.com>
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	glegroupsg2000goo.googlegroups.com; posting-host=65.13.115.246;
	posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
NNTP-Posting-Host:	65.13.115.246
References:	<201506091712 DOT t59HCPci004068 AT delorie DOT com> <557739E0 DOT 6070608 AT gmail DOT com>
	<CAB9Rao93XrKFBpUDnZdjCz+rEXHGOU2RNKdou2oMLJOk802LnA AT mail DOT gmail DOT com>
	<55775E64 DOT 2090901 AT gmail DOT com> <CAB9Rao-Njdr-CB=vqHnb+TVDmXu3eXqsB5CHB7V0kDwBEsM-WQ AT mail DOT gmail DOT com>
	<5579ED42 DOT 6070309 AT gmail DOT com> <bedfae3f-2695-4253-8d9c-11c55703f8b5 AT googlegroups DOT com>
	<557A0BD6 DOT 5090901 AT gmail DOT com> <557A1996 DOT 7040008 AT gmail DOT com>
User-Agent:	G2/1.0
MIME-Version:	1.0
Message-ID:	<e21dd871-7b83-471b-a5c0-af176c93353b@googlegroups.com>
Subject:	Re: Quake 2 DOS -- DJGGP 2.05 upgrade problems.
From:	"rugxulo AT gmail DOT com" <djgpp AT delorie DOT com>
Injection-Date:	Fri, 12 Jun 2015 01:35:22 +0000
Bytes:	2511
Lines:	20
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Hi,

On Thursday, June 11, 2015 at 6:28:34 PM UTC-5, Frank Sapone (emoaddict15 AT hates DOT spam) wrote:
> >>>
> >>> Another reason for
> >>> wanting to try out 2.05 is now the project is getting quite large and
> >>> I'm getting this warning at link time:
> >>>
> >>> "warning: .text: line number overflow: 0x10029 > 0xffff". I guess 2.03
> >>> has smaller limits for compiling a total project size?
> >> Is that (only) with debugging enabled? Yeah, older released (BinUtils
> >> before 2.23 ???) didn't have the COFF relocation extension hack.
> > Upgrading to the latest binutils fixed that issue, thanks for this.
> >>
> Actually, I noticed it worked well with removing that warning, but if I 
> run symify I get no backtrace, nothing updates.  This is with 2.03.  I 
> grabbed the binutils package from dec 2014.

That's a well-known issue from many years ago. I'm pretty sure that you're
supposed to use GDB's "bfdsymify" these days. Although keep in mind that
COFF debug info is somewhat broken, so it defaults to Dwarf 2 now.

- Raw text -