[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex
From: |
Eli Zaretskii |
Subject: |
Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex |
Date: |
Fri, 08 Apr 2022 22:16:50 +0300 |
> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Fri, 8 Apr 2022 13:56:31 +0100
> Cc: Tomas Kalibera <tomas.kalibera@gmail.com>, bug-texinfo@gnu.org
>
> What happens if we don't set MSYSTEM at all?
Then you cannot distinguish between MSYS and MinGW, because 'uname'
will return a value that doesn't tell which one is it. So you have a
problem, because MinGW needs the semi-colon as path separator, whereas
MSYS (being an emulation of Posix) needs the colon.
That's why the $OSTYPE trick.
> Methinks if MSYSTEM needs to be set correctly for uname to have the correct
> output, then the user will already have this set in their environment.
No, because 'uname' works when MSYSTEM is unset. It just reports a
value that is not MSYS specific.
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, (continued)
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Gavin Smith, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Tomas Kalibera, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Gavin Smith, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Tomas Kalibera, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Gavin Smith, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Tomas Kalibera, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Eli Zaretskii, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Eli Zaretskii, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Gavin Smith, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex, Eli Zaretskii, 2022/04/08
- Re: bug in texi2dvi, on Windows/Msys2 it cannot find tex,
Eli Zaretskii <=