From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with nm in binutils-2.25-2 on x86
Date: Fri, 09 Oct 2015 23:55:00 -0000 [thread overview]
Message-ID: <561853F4.8010009@gmail.com> (raw)
In-Reply-To: <5617DF99.7030701@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
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.
>
> That depends on what you mean by "everything in between". Wouldn't it
> suffice to rebuild the cygwin package and the toolchain?
>
> 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'.
>
I'll be rebuilding the CRT and cygwin gcc soon to give this a try.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-10-09 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 13:12 Ken Brown
2015-10-07 9:57 ` JonY
2015-10-08 9:35 ` JonY
2015-10-08 14:59 ` Ken Brown
2015-10-09 10:30 ` JonY
2015-10-09 15:38 ` Ken Brown
2015-10-09 23:55 ` JonY [this message]
2015-10-10 15:04 ` JonY
2015-10-11 4:25 ` JonY
2015-10-11 13:52 ` Ken Brown
2015-11-20 10:53 ` Marco Atzeri
2015-11-20 13:55 ` JonY
2015-11-24 18:24 ` Marco Atzeri
2015-11-25 2:29 ` JonY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=561853F4.8010009@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).