From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with nm in binutils-2.25-2 on x86
Date: Fri, 20 Nov 2015 10:53:00 -0000 [thread overview]
Message-ID: <564EFBB6.2010107@gmail.com> (raw)
In-Reply-To: <561A6992.8090401@cornell.edu>
On 11/10/2015 15:52, Ken Brown wrote:
> On 10/11/2015 12:25 AM, JonY wrote:
>> On 10/10/2015 23:04, JonY wrote:
>>> On 10/10/2015 07:55, JonY wrote:
>>>>
>>>> I'll be rebuilding the CRT and cygwin gcc soon to give this a try.
>>>>
>>>
>>> Nope, rebuilding the crt and Cygwin dll did not help at all.
>>>
>>
>> Updating binutils against git master seems to have solved the problem,
>> so new binutils version incoming.
>
> Confirmed. Thanks.
>
> Ken
>
I catched the same issue on x86_64
nm -l liboctave/.libs/cygoctave-3.dll
00000004c0aa6530 T zseri_
/pub/devel/octave/octave-4.0.0-2.x86_64/src/octave-4.0.0/liboctave/cruft/amos/zseri.f:1
00000004c0aa7090 T zshch_
/pub/devel/octave/octave-4.0.0-2.x86_64/src/octave-4.0.0/liboctave/cruft/amos/zshch.f:1
00000004c10f9f40 T zsyrk_BFD: Dwarf Error: Could not find abbrev number
1799.
00000004c10f9ac8 T ztrcon_BFD: Dwarf Error: Could not find abbrev number
1799.
00000004c10f9ac0 T ztrsyl_BFD: Dwarf Error: Could not find abbrev number
1799.
any plan to update also the x86_64 version ?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-11-20 10:53 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
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 [this message]
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=564EFBB6.2010107@gmail.com \
--to=marco.atzeri@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).