X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=PvKVTfCY5gxnTIcZ9HupGBXs7q9kV3uv0x2Awsc9b9I=;
	b=u5I7Bqy3TyXaWCo1FxFvu8VVYdnhzvVPtXYRYf0/zqvG9VqWeE2aMziYSyJQgORXIh
	rcoeNNhPzG8TtzqGCVnygi4WiA/5vzjMtNy2a+B+QGIjJKQvZAuKSHtdMXjIKRuHjljW
	zroMI+FKYsU9gxGuolcdvXMJxGkdlsYOHWeEmsoFCMYNJ8QGeM2nTj2ePhjVyqIkEjSk
	ofYfaN/ZEOkk1J27Og0eViU6nStrp/aTfa7btuas//0w3BHHxggA+6Xm12USXA0nxIHL
	bj8QtrCTDHwaTFWjqFv1UaEOZqMUgmSbadlRCq/4o4x0/efEn0UoTWdGnMrPbKrFhl+g
	rQGg==
X-Received:	by 10.42.85.207 with SMTP id r15mr13493543icl.94.1434065304304;
	Thu, 11 Jun 2015 16:28:24 -0700 (PDT)
Message-ID:	<557A1996.7040008@gmail.com>
Date:	Thu, 11 Jun 2015 19:28:22 -0400
From:	"Frank Sapone (emoaddict15 AT gmail DOT com)" <djgpp AT delorie DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: Quake 2 DOS -- DJGGP 2.05 upgrade problems.
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>
In-Reply-To:	<557A0BD6.5090901@gmail.com>
Reply-To:	djgpp AT delorie DOT com

>>> 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.

- Raw text -