From: Thomas Koenig <tkoenig@netcologne.de>
To: NightStrike <nightstrike@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: testsuite under wine
Date: Sat, 17 Dec 2022 11:52:29 +0100 [thread overview]
Message-ID: <19a6b738-ad34-d145-1202-d2c7c474b272@netcologne.de> (raw)
In-Reply-To: <CAF1jjLvJU2fnU0u0p9SwPre5mnhFdmv9pm_OvZGOvjQApCROqw@mail.gmail.com>
On 17.12.22 01:26, NightStrike wrote:
> On Fri, Dec 16, 2022 at 1:44 AM Thomas Koenig <tkoenig@netcologne.de> wrote:
>>
>> On 16.12.22 03:20, NightStrike via Fortran wrote:
>>
>>> When I run the testsuite under wine, I'm getting a lot of ANSI escape
>>> sequences. We had fixed this long ago, but it seems to be back. Any
>>> idea what I should change in my configuration to have this not happen?
>>
>> This should probably be fixed properly in some *.exp file, but you can
>> try setting the GCC_COLORS environment variable to an empty string
>> before running the test.
>
> That didn't help. It looks like this is always escape 25h to start
> the output and 25l to end it, which I think is turning the cursor on
> and off (based on https://en.wikipedia.org/wiki/ANSI_escape_code). I
> apparently fixed this previously by building wine with
> --without-curses
> (https://www.mail-archive.com/gcc@gcc.gnu.org/msg86366.html), but that
> option to wine was removed. Is there a way to hack this on the Deja
> side to ignore the escapes? Or to tell it to run in a way that makes
> wine not emit them?
Truth is, I don't know.
I have included the gcc mailing list in this reply, where more
knowledgeable people can be found :-)
next parent reply other threads:[~2022-12-17 10:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF1jjLtJW0juQR6L-VybJ8SSaqkfi=qN9FnxJVaY=oQBtkSLxA@mail.gmail.com>
[not found] ` <3f62bac2-ac1b-5c55-2488-ede2389d35d2@netcologne.de>
[not found] ` <CAF1jjLvJU2fnU0u0p9SwPre5mnhFdmv9pm_OvZGOvjQApCROqw@mail.gmail.com>
2022-12-17 10:52 ` Thomas Koenig [this message]
2022-12-17 23:24 ` NightStrike
2022-12-18 3:44 ` Jacob Bachmeyer
2022-12-18 21:13 ` NightStrike
2022-12-19 4:29 ` Jacob Bachmeyer
2022-12-19 10:43 ` Torbjorn SVENSSON
2022-12-19 11:00 ` NightStrike
2022-12-19 11:13 ` NightStrike
2022-12-20 3:51 ` Jacob Bachmeyer
[not found] ` <7cb45ab2-cc6e-c502-5592-51ffabcbc6f8@codeweavers.com>
2022-12-22 1:01 ` NightStrike
2022-12-22 4:37 ` Jacob Bachmeyer
2022-12-23 10:36 ` NightStrike
2022-12-23 12:43 ` Eric Pouech
2022-12-24 4:00 ` Jacob Bachmeyer
2022-12-24 11:05 ` Mark Wielaard
2023-01-05 2:50 ` NightStrike
2023-01-06 3:33 ` Jacob Bachmeyer
2023-01-06 3:44 ` Jerry D
2023-01-08 7:12 ` NightStrike
2023-01-11 2:30 ` Jacob Bachmeyer
2023-01-11 9:33 ` NightStrike
2023-01-12 4:11 ` Jacob Bachmeyer
2023-01-06 3:41 ` Jerry D
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=19a6b738-ad34-d145-1202-d2c7c474b272@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=nightstrike@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).