DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 56KIGLSS2027889
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1933A3858C41
Message-ID: <aeb04df0-b0c5-4548-8467-004427d4d2d1@SystematicSW.ab.ca>
Date: Sun, 20 Jul 2025 12:15:12 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: CMake is not finding a usable cc on my cygwin system, I've tried
 many things.
To: cygwin@cygwin.com
References: <CAGB_HuS1AEp3WGF5AANhtZyWnr+QdfbJZ3_egaaE1hM8QO6rig@mail.gmail.com>
 <fcf71e61-c511-4c67-9c33-d28d5574af09@SystematicSW.ab.ca>
 <CAGB_HuRfLZbQCWXRhjrhLOqkwh1Ohvh5zHkOhfO2J3uEGiMoXg@mail.gmail.com>
 <CAGB_HuRFp4RkiNaSGRA7=XOBZmXuA582G+P_Vi9PdQXz9jGWgQ@mail.gmail.com>
 <aHxsslcwZIFptjjq@slk15.local.net>
Content-Language: en-CA
Organization: Systematic Software
In-Reply-To: <aHxsslcwZIFptjjq@slk15.local.net>
Precedence: list
From: Brian Inglis via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On 2025-07-19 22:12, Duncan Roe via Cygwin wrote:
> On Sat, Jul 19, 2025 at 01:45:18PM -0400, ... wrote:
>> I just worked the CMake configuration command
>>     cmake -G"Unix Makefiles"
>> /cygdrive/C/Users/somia/Downloads/libjpeg-turbo-3.1.1/
>> and my woes were definitely due to having an msys cmake in my PATH. So,
>> guys, the guesses that I was trying with a Windows CMake were close but not
>> right on. It was *bash* that was my downfall, oddly enough. The first time
>> I invoked cmake I didn't have a cygwin cmake, and bash found the command
>> late in my PATH in the MSYS tree and hashed (stored) that path, so that
>> even after I installed cygwin cmake it kept calling msys cmake. Msys cmake
>> has now gone away for a lengthy vacation and cygwin cmake is producing a
>> configuration that is not quite successful but at least is more complete,
>> with real configure errors.

> Bash's `type` builtin would have told you that. `type` also tells you about
> aliases and functions, unlike `which` which I haven't used for ages.

Bash's which function tells you much more:

$ which which
which ()
{
     ( alias; declare -f ) | command which --tty-only --read-alias \
			--read-functions --show-tilde --show-dot "$@"
}

from which(1) or `info which example`. ;^>

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple