From: NightStrike <nightstrike@gmail.com>
To: Torbjorn SVENSSON <torbjorn.svensson@st.com>
Cc: "jcb62281@gmail.com" <jcb62281@gmail.com>,
Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>,
"dejagnu@gnu.org" <dejagnu@gnu.org>
Subject: Re: testsuite under wine
Date: Mon, 19 Dec 2022 06:00:46 -0500 [thread overview]
Message-ID: <CAF1jjLs7zgfLnwtXwXwRiANkRWw3=CaGbRgJhZMjdabhLxq=7A@mail.gmail.com> (raw)
In-Reply-To: <AM6PR10MB2197F5E3C814BA0FB568653E81E59@AM6PR10MB2197.EURPRD10.PROD.OUTLOOK.COM>
On Mon, Dec 19, 2022 at 5:43 AM Torbjorn SVENSSON
<torbjorn.svensson@st.com> wrote:
> I'm not sure if this helps anyone, but I experienced something similar with Cygwin a while back.
> What I had to do in order to have expect working when testing GCC on Windows 10 was to defined the "CYGWIN" environment variable to "disable_pcon" (https://cygwin.com/cygwin-ug-net/using-cygwinenv.html). If I did not define this variable, then Cygwin would inject an escape sequence that would make all pattern checks fail on the output.
>
> I don't know if Cygwin might has changed this behavior, but it was an issue in the past anyway.
This is extremely helpful for when I start testing natively, thank
you. I think in general the problem is the same, but Wine doesn't
immediately have a comparable workaround.
next prev parent reply other threads:[~2022-12-19 11:00 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
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 [this message]
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='CAF1jjLs7zgfLnwtXwXwRiANkRWw3=CaGbRgJhZMjdabhLxq=7A@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=dejagnu@gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jcb62281@gmail.com \
--cc=tkoenig@netcologne.de \
--cc=torbjorn.svensson@st.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).