NightStrike wrote:
On Tue, Jan 10, 2023 at 9:30 PM Jacob Bachmeyer wrote:
NightStrike wrote:
[...]
I did another little test to try to better understand your point. I
ran a linux native testsuite under a simulator that just sets SIM to "
". This resulted in extra ^M's also, although
On Tue, Jan 10, 2023 at 9:30 PM Jacob Bachmeyer wrote:
>
> NightStrike wrote:
> > [...]
> > I did another little test to try to better understand your point. I
> > ran a linux native testsuite under a simulator that just sets SIM to "
> > ". This resulted in extra ^M's also, although many tests
NightStrike wrote:
[...]
I did another little test to try to better understand your point. I
ran a linux native testsuite under a simulator that just sets SIM to "
". This resulted in extra ^M's also, although many tests pass because
they're already looking for \r\n to accommodate windows. So
On Thu, Jan 5, 2023 at 10:33 PM Jacob Bachmeyer wrote:
>
> NightStrike wrote:
> > On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote:
> >
> >> NightStrike wrote:
> >>
> >>> On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer
> >>> wrote:
> >>>
> [...]
> >>> So at least we know for sure
On 1/5/23 7:33 PM, Jacob Bachmeyer via Fortran wrote:
NightStrike wrote:
On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer
wrote:
NightStrike wrote:
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer
wrote:
[...]
So at least we know for sure that this particular instance of extra
characters
On 1/4/23 6:50 PM, NightStrike via Fortran wrote:
On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote:
NightStrike wrote:
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
NightStrike wrote:
[...]
Second, the problems with extra \r's still remain, but I think we've
generally come
NightStrike wrote:
On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote:
NightStrike wrote:
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
[...]
So at least we know for sure that this particular instance of extra
characters is coming from Wine. Maybe Wine can be
On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote:
> NightStrike wrote:
> > On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
> >> NightStrike wrote:
> >>
> >>> [...]
> >>> Second, the problems with extra \r's still remain, but I think we've
> >>> generally come to think that that
Hi,
On Fri, Dec 23, 2022 at 10:00:36PM -0600, Jacob Bachmeyer via Gcc wrote:
> NightStrike wrote:
> > Rust is getting \r\r\n\n (as opposed to \r\n\r\n), so... yeah. Could
> > be the rust test, could be the rust frontend, could be another weird
> > Wine interaction.
>
> That is probably either
NightStrike wrote:
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
NightStrike wrote:
[...]
Second, the problems with extra \r's still remain, but I think we've
generally come to think that that part isn't Wine and is instead
either the testsuite or deja. So I'll keep those
Le 23/12/2022 à 11:36, NightStrike a écrit :
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
NightStrike wrote:
[...]
Second, the problems with extra \r's still remain, but I think we've
generally come to think that that part isn't Wine and is instead
either the testsuite or deja. So
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote:
>
> NightStrike wrote:
> > [...]
> > Second, the problems with extra \r's still remain, but I think we've
> > generally come to think that that part isn't Wine and is instead
> > either the testsuite or deja. So I'll keep those replies to
NightStrike wrote:
[...]
Second, the problems with extra \r's still remain, but I think we've
generally come to think that that part isn't Wine and is instead
either the testsuite or deja. So I'll keep those replies to Jacob's
previous message.
Most likely, it is a combination of the MinGW
On Wed, Dec 21, 2022 at 12:38 PM Jacek Caban wrote:
>
> Hi all,
>
>
> I'm responsible for Wine changes that cause your problems. I'm also
> CCing Eric, who is Wine console expert, maybe he has better ideas. Eric,
> see [1] if you're interested in the context.
>
>
> Recent Wine versions implement
NightStrike wrote:
On Sun, Dec 18, 2022 at 11:29 PM Jacob Bachmeyer wrote:
NightStrike wrote:
On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
[...]
This is either a testsuite problem or an environment problem. The GNU
Fortran I/O module certainly has interesting
On Sun, Dec 18, 2022 at 11:29 PM Jacob Bachmeyer wrote:
>
> NightStrike wrote:
> > On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
> >
> >> [...]
> >> This is either a testsuite problem or an environment problem. The GNU
> >> Fortran I/O module certainly has interesting behavior here.
On Mon, Dec 19, 2022 at 5:43 AM Torbjorn SVENSSON
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
ist ; deja...@gnu.org
> Subject: Re: testsuite under wine
>
> NightStrike wrote:
> > On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer
> wrote:
> >
> >> [...]
> >> This is either a testsuite problem or an environment problem. The GNU
> >> Fortran I/
NightStrike wrote:
On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer 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
ig
> >>> 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 fix
NightStrike wrote:
On Sat, Dec 17, 2022 at 5:52 AM Thomas Koenig wrote:
On 17.12.22 01:26, NightStrike wrote:
On Fri, Dec 16, 2022 at 1:44 AM Thomas Koenig wrote:
On 16.12.22 03:20, NightStrike via Fortran wrote:
When I run the testsuite under wine, I'm getting
On Sat, Dec 17, 2022 at 5:52 AM Thomas Koenig wrote:
>
> On 17.12.22 01:26, NightStrike wrote:
> > On Fri, Dec 16, 2022 at 1:44 AM Thomas Koenig wrote:
> >>
> >> On 16.12.22 03:20, NightStrike via Fortran wrote:
> >>
> >>> When I run the tes
On 17.12.22 01:26, NightStrike wrote:
On Fri, Dec 16, 2022 at 1:44 AM Thomas Koenig 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
On Thu, Sep 6, 2018 at 4:58 PM NightStrike wrote:
>
> On Thu, Sep 6, 2018 at 9:08 AM NightStrike wrote:
> >
> > Host: x86_64-pc-linux (Cent 6)
> > Target: x86_64-w64-mingw32 (wine)
> >
> > When I build the linux > w64 cross compiler under linux and r
On Thu, Sep 6, 2018 at 9:08 AM NightStrike wrote:
>
> Host: x86_64-pc-linux (Cent 6)
> Target: x86_64-w64-mingw32 (wine)
>
> When I build the linux > w64 cross compiler under linux and run the
> testsuite under wine, it all basically works for the most part.
> However,
Host: x86_64-pc-linux (Cent 6)
Target: x86_64-w64-mingw32 (wine)
When I build the linux > w64 cross compiler under linux and run the
testsuite under wine, it all basically works for the most part.
However, the log files get filled with what appears to be ANSI escape
sequences of the form:
^[[
26 matches
Mail list logo
