Re: Trying to figure out what is wrong in a colleague's Cygwin setup

[David Karr <davidmichaelkarr@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

Actually, I was mistaken. I was given incomplete information. I'm getting
much of this second hand. Adding that to the PATH made no difference.

It appears this is something specific to "kubectl".  They ended up setting
the KUBECONFIG environment variable to "C:\Users\<uid>\.kube\config", which
is very odd, as that is basically the default value of it, and I have never
set that, and I've never seen this problem. Whatever. They're working now.

On Fri, Jun 16, 2023 at 12:17 PM Mike Gran <spk121@yahoo.com> wrote:

> > Ok, well, we managed to resolve this, but I don't understand why what we
> > did would fix this.
>
> > In system environment variables in Windows, they added "c:\cygwin64\bin"
> to
> > the end of the PATH. That fixes the problem. That just doesn't make any
> > sense to me. In a Cygwin shell, "/usr/bin" is in the PATH, which is the
> > same as "c:\cygwin64\bin".
>
> Hello David-
> The fact that their uname said MINGW implies they weren't running
> "real" Cygwin, but, actually MSYS, which is the slightly modified Cygwin
> that is bundled with MINGW to allow it to run bash and other
> coreutils.
>
> MSYS has its own location for '/usr/bin', which is probably
> c:/msys64/usr/bin or similar. It won't look in c:/cygwin64 by default.
>
> Just a guess, but, hope this helps.
> -Mike Gran
>