From: Oleg Tolmatcev <oleg.tolmatcev@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] ld: fix 32-bit mingw DLL symbol export bug
Date: Fri, 19 Jan 2024 17:07:14 +0100 [thread overview]
Message-ID: <CACcXsZiOt+BLYaAwFpBjRfBJM13uOuveyT93Ban+rT5ewR8tPg@mail.gmail.com> (raw)
In-Reply-To: <520ddb1b-b98d-43b9-b9af-b3eb46711b90@redhat.com>
Am Fr., 19. Jan. 2024 um 16:06 Uhr schrieb Nick Clifton <nickc@redhat.com>:
> I have gone ahead and applied the patch. I am not an expert
> on win32 function call APIs, so I am assuming that your patch
> is correct. If people start to complain, then we will have to
> take another look. :-)
Thanks. Can you close this ticket
https://sourceware.org/bugzilla/show_bug.cgi?id=21033? I fixed it in
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=6aadf8a04d162feb2afe3c41f5b36534d661d447.
Best regards
Oleg Tolmatcev
prev parent reply other threads:[~2024-01-19 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 14:24 Oleg Tolmatcev
2024-01-16 20:40 ` Oleg Tolmatcev
2024-01-19 11:40 ` Nick Clifton
2024-01-19 12:34 ` Oleg Tolmatcev
2024-01-19 15:06 ` Nick Clifton
2024-01-19 16:07 ` Oleg Tolmatcev [this message]
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=CACcXsZiOt+BLYaAwFpBjRfBJM13uOuveyT93Ban+rT5ewR8tPg@mail.gmail.com \
--to=oleg.tolmatcev@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).