From: Ulf Hermann <ulf.hermann@qt.io>
To: "McAllister, Colin" <Colin.McAllister@garmin.com>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Building Elfutils with Mingw32
Date: Fri, 15 Sep 2023 08:57:46 +0200 [thread overview]
Message-ID: <df506e81-cfba-a4db-cd90-8e9651dea6c9@qt.io> (raw)
In-Reply-To: <SA2PR04MB7723D417EE6FB634173B9CC3F4F7A@SA2PR04MB7723.namprd04.prod.outlook.com>
Indeed I have noticed the other patches, but I don't think they are the
same as mine. So, now we have a three way merge.
I guess some more of the changes could be merged if properly cleaned up
and made to benefit other obscure platforms, too. However, there are a
few I got a definite "no" for. In particular the windows dance around
text/binary mode when opening files was not welcome. I couldn't come up
with a better solution than adding an O_BINARY or O_TEXT to every single
open() call. We actually need the distinction as some files need to be
opened in text mode for the tests to pass. If you can come up with
anything better here, please let me know.
best regards,
Ulf
next prev parent reply other threads:[~2023-09-15 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 21:08 McAllister, Colin
2023-09-13 21:34 ` Frank Ch. Eigler
2023-09-14 6:34 ` Ulf Hermann
2023-09-14 19:44 ` McAllister, Colin
2023-09-15 6:57 ` Ulf Hermann [this message]
2023-09-15 15:42 ` McAllister, Colin
2023-09-15 21:00 ` Mark Wielaard
2023-09-16 7:17 ` Ulf Hermann
2023-09-16 7:33 ` Ulf Hermann
2023-11-01 13:05 ` Mark Wielaard
2023-09-16 19:24 ` Milian Wolff
2023-09-18 13:18 ` McAllister, Colin
2023-09-18 15:45 ` Frank Ch. Eigler
2023-11-01 13:15 ` Mark Wielaard
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=df506e81-cfba-a4db-cd90-8e9651dea6c9@qt.io \
--to=ulf.hermann@qt.io \
--cc=Colin.McAllister@garmin.com \
--cc=elfutils-devel@sourceware.org \
/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).