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 beha
Jonathan Wakely wrote:
Is there a reason that dejagnu's local_exec proc doesn't use the
-noecho option for spawning the command?
Every log contains the spawned commands twice because dejagnu prints
it then spawn repeats it (with an annoying \r appended, making copy &
paste from the logs more awk
Is there a reason that dejagnu's local_exec proc doesn't use the
-noecho option for spawning the command?
Every log contains the spawned commands twice because dejagnu prints
it then spawn repeats it (with an annoying \r appended, making copy &
paste from the logs more awkward than it needs to be)
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. T
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 "d
Hi,
> -Original Message-
> From: dejagnu-bounces+torbjorn.svensson=st@gnu.org bounces+torbjorn.svensson=st@gnu.org> On Behalf Of Jacob Bachmeyer
> Sent: den 19 december 2022 05:29
> To: NightStrike
> Cc: Thomas Koenig ; fort...@gcc.gnu.org; gcc
> mailing list ; dejagnu@gnu.org
>
