From: Nick Clifton <nickc@redhat.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org,
mingw-w64-public@lists.sourceforge.net
Subject: Re: Problems when building NT kernel drivers with GCC / LD
Date: Wed, 12 Apr 2023 10:53:32 +0100 [thread overview]
Message-ID: <09fd1c9d-6f3c-b1c0-4692-cb1d35fae2a1@redhat.com> (raw)
In-Reply-To: <20230401092350.isnr5aa7d3clmmhw@pali>
Hi Pali,
>> Hello! Just for a record, I filled individual issues to bugzilla:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30004
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30139
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30140
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30141
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30142
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30143
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30144
>> https://sourceware.org/bugzilla/show_bug.cgi?id=30145
>
> Hello! Should I do something more regarding these issues?
Hitting me with a big hammer ?
*sigh* I was really hoping that someone else would step up to look at these
issues as I am not a Windows expert.
It looks like the first one (30004) has been fixed, and 30140 may have been
resolved - assuming that you agree with the explanation in comment #2. But
the others all need addressing. I will try to make time for them in the next
few weeks.
If you do have any suggestions for fixes to any of these problems, please do
feel free to add them to the relevant bug reports.
Cheers
Nick
next prev parent reply other threads:[~2023-04-12 9:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 0:06 Pali Rohár
2022-10-30 7:06 ` [Mingw-w64-public] " Martin Storsjö
2022-10-30 19:58 ` ralph engels
2022-10-31 9:55 ` Jan Beulich
2022-11-05 0:57 ` Pali Rohár
2022-11-05 1:26 ` Pali Rohár
2022-11-20 13:10 ` Pali Rohár
2022-11-21 7:24 ` Jan Beulich
2022-11-26 19:04 ` Pali Rohár
2022-11-28 8:07 ` Jan Beulich
2022-11-28 8:40 ` Jonathan Wakely
2022-11-28 9:06 ` Jan Beulich
2022-12-26 10:47 ` Pali Rohár
2023-01-03 11:06 ` Nick Clifton
2023-02-20 18:25 ` Pali Rohár
2023-04-01 9:23 ` Pali Rohár
2023-04-12 9:53 ` Nick Clifton [this message]
2023-04-12 20:40 ` Pali Rohár
2024-01-07 1:55 ` Pali Rohár
2024-04-07 23:20 ` Pali Rohár
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=09fd1c9d-6f3c-b1c0-4692-cb1d35fae2a1@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=mingw-w64-public@lists.sourceforge.net \
--cc=pali.rohar@gmail.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).