bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/20880] [LD] [Bug] Wrong Hint Value For ImportLib IDATA6


From: rudyy.id at gmail dot com
Subject: [Bug binutils/20880] [LD] [Bug] Wrong Hint Value For ImportLib IDATA6
Date: Thu, 01 Dec 2016 20:17:50 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=20880

--- Comment #5 from Rudy Y. <rudyy.id at gmail dot com> ---
Nick...Thanks but sorry, I didn't online couple a days.
I don't know how, but that patch won't fix the problem. For the past
couple of days, I'm still looking whats make ld generate different
ordinal between def file and import lib, so thats why I didn't go
online and didn't check my email until today (2016/12/01 GMT).

I used this command:
gcc -shared foo.c -Wl,--output-def,foo.def -Wl,--out-implib,foo.a -o foo.dll

Its possible from "ld/pe-dll.c->generate_edata" since there is a code
in there that could lead ordinal number start from zero when
min_ordinal = 1.
But I didn't check for more because I'm stress out from testing and
recompile (a lot).
So maybe you or someone else can chek for more, perhaps. Thanks.

I'm replying this since my bug report for that has gone.

On Thu, Dec 1, 2016 at 4:15 PM, nickc at redhat dot com
<address@hidden> wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=20880
>
> Nick Clifton <nickc at redhat dot com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>                  CC|                            |nickc at redhat dot com
>          Resolution|---                         |FIXED
>
> --- Comment #4 from Nick Clifton <nickc at redhat dot com> ---
> Hi Rudy,
>
>   Thanks for the problem description and patch.  I have now applied your
>   suggested fix.
>
> Cheers
>   Nick
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]