CMake is not finding a usable cc on my cygwin system, I've tried many things.
Brian Inglis
Brian.Inglis@SystematicSW.ab.ca
Sun Jul 20 18:15:12 GMT 2025
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
More information about the Cygwin
mailing list