DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=mwyijy
	Jc+5x5LYDjOMHeLeSF612sj7Qj92zGiI5DNdVUOy3tiXnl6skeGw/3Pcq2D2FJfX
	99iwcXP7Js7AE6Dtq77N3PZmxcC8E6hdhyElwc53ZxrqNdxFhL6+ay9wdG/op2Wn
	Wrq8d1W7sVNHDSkb/5YsRuS/1E8GY4U2EsVBE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <561853F4.8010009@gmail.com>
Date: Sat, 10 Oct 2015 07:55:32 +0800
From: JonY <10walls AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.4) Gecko/20150524 FossaMail/25.1.5
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Problem with nm in binutils-2.25-2 on x86
References: <5613C8B0 DOT 5060604 AT cornell DOT edu> <5614EC94 DOT 7080500 AT gmail DOT com> <561638C5 DOT 90503 AT gmail DOT com> <561684E7 DOT 5010608 AT cornell DOT edu> <5617974E DOT 10705 AT gmail DOT com> <5617DF99 DOT 7030701 AT cornell DOT edu>
In-Reply-To: <5617DF99.7030701@cornell.edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L2d51xsgWjqqllhfovX04FU1tvxsESnFp"

--L2d51xsgWjqqllhfovX04FU1tvxsESnFp
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 10/9/2015 23:39, Ken Brown wrote:
> On 10/9/2015 6:30 AM, JonY wrote:
>>
>>> $ nm -l a.exe
>>> 00406000 b .bssBFD: Dwarf Error: Could not find abbrev number 120.
>>> 00406018 b .bssBFD: Dwarf Error: Could not find abbrev number 120.
>>> [...]
>>> 00406040 b _u.25303BFD: Dwarf Error: Could not find abbrev number 120.
>>> 00401000 T _WinMainCRTStartup
>>> /usr/src/debug/cygwin-2.2.1-1/winsup/cygwin/crt0.c:23
>>> 004070b8 i fthunkBFD: Dwarf Error: Could not find abbrev number 120.
>>> 00407074 i hnameBFD: Dwarf Error: Could not find abbrev number 120.
>>>
>>> Ken
>>
>> Kai is of the opinion that rebuilding the gcc, CRT, Cygwin and
>> everything in between be rebuilt with the new binutils to solve the
>> issue.
>>
>> Might be a huge undertaking.
>=20
> That depends on what you mean by "everything in between".  Wouldn't it
> suffice to rebuild the cygwin package and the toolchain?
>=20
> The main issue for us, AFAICT, is that package maintainers need to be
> able to build their packages without having the build take hours when
> cygport calls 'nm -l'.
>=20

I'll be rebuilding the CRT and cygwin gcc soon to give this a try.


--L2d51xsgWjqqllhfovX04FU1tvxsESnFp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJWGFP8AAoJEHE7X+KcFF1FXrUP/1VTdnA2Q26SXdPOYML9suGs
sXFMYOYQ5qHfaCuaRYQkIzyQua68WJEf8HGJlJ2VJmeRXQ3IimARRm0gmQodywA0
C33vWRpJCTP4qbygr6JCsYmutw1Ya24FiK6bcrIpWzwowKqUlnVKRMX8jYh10W73
WsE/MCW8gdurhbocTWE+sY6Lra0tarctN8g8f/4JEmWRA2Lev6ntP2a5G1H+mlfu
POIwMmd93VCvVWOLvO8iJo13s/tVGuFxzIWeuD3MZlt4djuUbeFO+P7gBdK4ClrL
NdMdbWURC1jxAxhsgq8U5X9jypJPbx0YwC77wy1zXBFXBSGUPmKxoZqBa/BoLg4n
4eL7g+ugxZ39s1vNt3CrVvb8A6F+0H5tiOs/798o905m+g/xkmewFepRRjq2OyxD
nuO02dgEv+z5A5h8zSozHiwIDGkVsPxvk2foc4X1BceM8Pn+kIxQILpNHFdOZA2S
fP4q5iUmGjTprmVywAgRVuUGsmwP0D2qPoytgBge8YJJj7snsNbuK1foFyN6mGHN
Mf3bZdGlin51/ZgYP0X1mUv1i1vRdGEPgZTpTOyx7zKxr3jEAjqjqn1Wq6nbz3kB
r4Q3TdfNvQfctijpZ+UI3EOdZ44RMRsaoq8oS3Cb9uzhzmt7GWI+XLgegHbrNPLJ
Z6Fc9Lg3AWL0FBoQTflt
=5WAW
-----END PGP SIGNATURE-----

--L2d51xsgWjqqllhfovX04FU1tvxsESnFp--