Hi, > -----Original Message----- > From: dejagnu-bounces+torbjorn.svensson=st....@gnu.org <dejagnu- > bounces+torbjorn.svensson=st....@gnu.org> On Behalf Of Jacob Bachmeyer > Sent: den 19 december 2022 05:29 > To: NightStrike <nightstr...@gmail.com> > Cc: Thomas Koenig <tkoe...@netcologne.de>; fort...@gcc.gnu.org; gcc > mailing list <gcc@gcc.gnu.org>; deja...@gnu.org > Subject: Re: testsuite under wine > > NightStrike wrote: > > On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer > <jcb62...@gmail.com> wrote: > > > >> [...] > >> This is either a testsuite problem or an environment problem. The GNU > >> Fortran I/O module certainly has interesting behavior here. Try setting > >> TERM=dumb in the environment while running the testsuite. If that fixes > >> the problem, it may be appropriate to add "set ::env(TERM) dumb" to the > >> tool init file for GNU Fortran. > >> > > > > Setting TERM doesn't help. Wine tries to emulate the windows console, > > which requires outputting this stuff. It does so any time there's a > > pty, and I believe that Deja creates a pty when running the tests. > > > > That is a bug in Wine: the escapes should be suppressed entirely if the > terminal does not support them---and the "dumb" terminal does not > support them.
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. Kind regards, Torbjörn
