From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Cc: Kai Tietz <ktietz70@googlemail.com>
Subject: Re: Problem with nm in binutils-2.25-2 on x86
Date: Thu, 08 Oct 2015 09:35:00 -0000 [thread overview]
Message-ID: <561638C5.90503@gmail.com> (raw)
In-Reply-To: <5614EC94.7080500@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On 10/7/2015 17:57, JonY wrote:
> On 10/6/2015 21:12, Ken Brown wrote:
>> This is a followup to
>> https://www.cygwin.com/ml/cygwin/2015-10/msg00059.html .
>>
>> I tried to build icu using gcc-5 and binutils-2.25-2 on x86. The build
>> appeared to hang when cygport was stripping executables. I traced the
>> problem to a call to 'nm -l' in src_postinst.cygpart. This produced
>> errors like the following when called on some of the DLLs:
>>
>> $ nm -l cygicui18n56.dll
>> 6270c458 b .bssBFD: Dwarf Error: Could not find abbrev number 1151.
>> 6270c594 b .bssBFD: Dwarf Error: Could not find abbrev number 1151.
>> 6270c0cc b .bssBFD: Dwarf Error: Could not find abbrev number 1151.
>> ...
>>
>> This particular DLL can be found at
>>
>> http://sanibeltranquility.com/cygwin/cygicui18n56.dll.xz
>>
Hi Ken,
Are you able to reproduce a test case? Seems to require some complexity
to trigger it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-10-08 9:35 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 [this message]
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
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=561638C5.90503@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
--cc=ktietz70@googlemail.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).