DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 56JH4PuH667425
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 56JH4PuH667425
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=yne31bJ3
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 90C9B385780C
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1752944663;
	bh=ZagGN/wxdd/SBd7I/IezTn8DJRGZbT0EUCtcYCnWZNs=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=yne31bJ35dBOc/DT2IM/bOoyYijLiK3sHyQpCreROxMZfaMsfTZGvPjtaq8BsZ4mA
	Fg8Gl5e5onFbYL6xpz/GcAuRPXxmdHVIJRVY7KQiiVQcsjtCSO+OXLdd9ggukFH7Xg
	ZXmkoge/qSIRiCwJStQmHrwOlgcF0lN8jBHazZls=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 9419D3858C66
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 9419D3858C66
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1752944605; cv=none;
	b=TjQ13Z3B+jtreJKHa0wSHGTTI0Gum7IKupkYtDDvVhbx1JvirBUb9HJOxgWA50jwTAxYDgayvjxxhg6ZaQGBlWrvWYtIV+HDBNpW7VxRUNdyAmnxYd6Ulzpcs7io5HQtqeWMSsbhZLlv/XwYcFVI0SRw5ElQmfO1sfDhzH/evSw=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1752944605; c=relaxed/simple;
	bh=orud+XJWTPgDMcCAaH/kphDstdWxXI3JC5eKL15C7Co=;
	h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To;
	b=gTp5PHVcxTno7pC+6SMdIh8PiOWPl0rstPt4SwmFKGAOAVUXIHn1xM7Ggc9qib0bnD0hSbzamWHYMqtoBUutjRsJ3W6+CgQjHOZDS1LcLg3tY+As5ZGm8IWEOgM/mYVDRQZ1Il4Cg24Y2MChXa3uT5QqNMySpB9dv0UX/7BNkHo=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 9419D3858C66
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20230601; t=1752944602; x=1753549402;
	h=to:subject:message-id:date:from:in-reply-to:references:mime-version
	:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
	bh=sZMdnuWkOrG7tJt7XD2pY6q+GS6zCIgiZ26ui9f8UDY=;
	b=LFT3FxuMe9z7lkxdaZ990Vtc2ZN5ZhQKs1nvyUoG96CwCTAM8kSoqcZH4Yih3LihuG
	FS08gxlhjxPN1rbiLhrVUK3SEMI+5AljuGzBr7hGH2KGmOB/VWh4trKslaNmoG+sxwpy
	7J2LukegkzCpSAC+/lwVAsEW2ICDqvaC9ks4et0hE0TDUq6nWQnfDBP80IPdb0JN4SKq
	ujqmoBMr5ZGB5j/Emq6VMsHroCI+Cje9VUguUoE7UAWRyShl0BTM8regIRFt5E0ZfINS
	fi4Ek1UP4UH6p92k5Dh4zal8vswx99CMYrvq2FaHlBiI2uUdd+GG+zUUgjhnLGwUSvGJ
	MVdg==
X-Gm-Message-State:	AOJu0YzZ9t7StTUMcnjr5nyvhuSu/4VCBzASU7k/Pviu4Ia1OYCGWDE3
	3HGvDFB9NbYSmXH9r7NjGhy2+zq3WvR6B9o2ZMbBFI99atyfCKZ30lI9WBY0AwSc3xPLtWBhzgR
	NsDnB1IbelTuNz8UFq1NpPxFvZWw7BrvM7+C8
X-Gm-Gg:	ASbGncv3x5Cabz3zSWMDfL5zJNJCRxxthL6jVyY7tCEVZ3QCQf6kudBVI2ws8K0dVpy
	GbMmP7FGTvyPGoZeU4kzCjH+vg0KuYKD4Q+E3W6QpG/xzY/pNkYeYjZdQVl1TFU6uUhzlRH5yjT
	TTKehmah4iIVgTSqM9DZun4lHET9lnkXCl+I1F4JIIZBD1H1auLcNHjOASsGHq6LSw7K8ZJ20VC
	xww
X-Google-Smtp-Source:	AGHT+IH03PUWnVe9E4P3z3QxJb0vaHsAYbXkQby8NbzCqw8Uv4qlw3P12qLw163eysaj1v6ehmJ1qJMUKxFug0zx3Mk=
X-Received:	by 2002:a2e:bc1a:0:b0:32c:ef7a:cbd7 with SMTP id
	38308e7fff4ca-3308f653f77mr38220971fa.36.1752944602240; Sat, 19 Jul 2025
	10:03:22 -0700 (PDT)
MIME-Version:	1.0
References:	<CAGB_HuS1AEp3WGF5AANhtZyWnr+QdfbJZ3_egaaE1hM8QO6rig AT mail DOT gmail DOT com>
	<fcf71e61-c511-4c67-9c33-d28d5574af09 AT SystematicSW DOT ab DOT ca>
In-Reply-To:	<fcf71e61-c511-4c67-9c33-d28d5574af09@SystematicSW.ab.ca>
Date:	Sat, 19 Jul 2025 13:03:06 -0400
X-Gm-Features:	Ac12FXzu10HRZzGdLVf6uUDSpSGSfixzNcxIacbXDApWSCydPYviYExOc4gFCVs
Message-ID:	<CAGB_HuRfLZbQCWXRhjrhLOqkwh1Ohvh5zHkOhfO2J3uEGiMoXg@mail.gmail.com>
Subject:	Re: CMake is not finding a usable cc on my cygwin system, I've tried
	many things.
To:	cygwin AT cygwin DOT com
X-Content-Filtered-By:	Mailman/MimeDel 2.1.30
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Soren via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Soren <somian08 AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 56JH4PuH667425

In reply to Brian Inglis, with acknowledgement to Kevin Schnitzius for his
reply also.
There's nothing in my setup that I know of that would account for this odd
behavior. CMake is munging the paths tools in the configuration stage of
its operation. OK, point  by point (much detail follows):
On Fri, Jul 18, 2025 at 7:36 PM Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
wrote:

> On 2025-07-18 16:14, Soren via Cygwin wrote:
> > Hello Cygwinstas,
> >
> > Cygwin root is C:\ix\cygwin, just so you know.
> >
> > This is the output I see: mintty screen dump:
> >
> > $ cmake -G"Unix Makefiles" C:/Users/somia/Downloads/libjpeg-turbo-3.1.1/
> > cmake -G"Unix Makefiles" C:/Users/somia/Downloads/libjpeg-turbo-3.1.1/
> > -- The C compiler identification is GNU 12.5.0
> > -- Detecting C compiler ABI info
> > -- Detecting C compiler ABI info - failed
> > -- Check for working C compiler: /c/ix/cygwin/bin/cc
> > -- Check for working C compiler: /c/ix/cygwin/bin/cc - broken
> > CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:67
> (message):
> >    The C compiler
> >
> >      "/c/ix/cygwin/bin/cc"
> >
> >    is not able to compile a simple test program.
> >   It fails with the following output:
> >   Change Dir:
> '/c/Users/somia/build/libjpeg-turbo/CMakeFiles/CMakeScratch/TryCompile-PYyzjN'
> >
> >      Run Build Command(s): /usr/bin/cmake.exe -E env VERBOSE=1
> > /c/perl/c/bin/gmake.exe -f Makefile cmTC_de473/fast
> >      C:/perl/c/bin/gmake  -f CMakeFiles/cmTC_de473.dir/build.make
> > CMakeFiles/cmTC_de473.dir/build
> >      gmake[1]: Entering directory
> >
> 'C:/Users/somia/build/libjpeg-turbo/CMakeFiles/CMakeScratch/TryCompile-PYyzjN'
> >      Building C object CMakeFiles/cmTC_de473.dir/testCCompiler.c.o
> >      /c/ix/cygwin/bin/cc    -o
> > CMakeFiles/cmTC_de473.dir/testCCompiler.c.o -c
> >
> /c/Users/somia/build/libjpeg-turbo/CMakeFiles/CMakeScratch/TryCompile-PYyzjN/testCCompiler.c
> >      /usr/bin/sh: /c/ix/cygwin/bin/cc: No such file or directory
> >      gmake[1]: *** [CMakeFiles/cmTC_de473.dir/build.make:78:
> > CMakeFiles/cmTC_de473.dir/testCCompiler.c.o] Error 127
> >      gmake[1]: Leaving directory
> >
> 'C:/Users/somia/build/libjpeg-turbo/CMakeFiles/CMakeScratch/TryCompile-PYyzjN'
> >      gmake: *** [Makefile:127: cmTC_de473/fast] Error 2
> >
> >
> >    CMake will not be able to correctly generate this project.
> > Call Stack (most recent call first):
> >    CMakeLists.txt:16 (project)
> >
> > -- Configuring incomplete, errors occurred!
> >
> > If I clean out all cached data in my build dir and set `CC=/bin/gcc';
> > export CC' is get another error:
> >
> > cmake -G"Unix Makefiles" C:/Users/somia/Downloads/libjpeg-turbo-3.1.1/
> > CMake Error at /usr/share/cmake/Modules/CMakeDetermineCCompiler.cmake:49
> > (message):
> >    Could not find compiler set in environment variable CC:
> >    /bin/gcc.
> > Call Stack (most recent call first):
> >    CMakeLists.txt:16 (project)
> >
> > CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
> > -- Configuring incomplete, errors occurred!
> >
> >    I hear people saying good things about CMake but this is maddening.
> > My cmake is newly installed in /usr/bin/cmake and is version 3.30.1
> >
> > I'm trying to build libjpeg-turbo as my pathnames above would suggest.
>
> Cygwin current cmake is 3.31.3.
> It looks like you are running a Windows cmake.
> Try:
>
> $ which -a cmake
> /usr/bin/cmake
>
Yes, that is my cmake, Brian. Here's what `cygcheck' says:

$ cygcheck -i --inst cmake
Fetching setup.ini from cygwin.com...
Installed package:
------------------

Name        : cmake
Version     : 3.28.3
Release     : 1
Architecture: x86_64
Install Date: Fri Jul 18 13:18:25 2025
Size        : 14383900 (14 M)
Categories  : Devel
Source      : cmake-3.28.3-1-src.tar.xz
Summary     : Cross-platform makefile generation system

...
Cygcheck -i --curr says the current (latest) cmake is what I have:

Latest available package:
-------------------------

Name        : cmake
Version     : 3.28.3


Are you using a testing release of cmake, Brian?

I have two cmakes, according to which -a cmake:

which -a cmake
/usr/bin/cmake
/cygdrive/c/ix/msys64/usr/bin/cmake


/cygdrive/c/ix/msys64/usr/bin/cmake --version
cmake version 3.30.1


I don't know why or how, that msys64 path-element comes very near the end
of my PATH, but when I cited "3.30.1" as my cmake version in my initial
message, that must have been the one I was picking up. I am going to move
that msys cmake out and away just to make sure it isn't the one trying to
configure for me.

About gcc:

$ ls -Ggl /bin/cc
> lrwxrwxrwx 1 7 Aug  2  2024 /bin/cc -> gcc.exe
>
> I get the positive output corresponding to yours:

lrwxrwxrwx 1 7 Jul 18 13:18 /bin/cc -> gcc.exe*


Are you running from a Cygwin terminal+/-shell, did you run Cygwin.bat, or
> set
> up a DOS/cmd environment with Cygwin bin at the start of your PATH?
>
> I am running from the mintty terminal with bash from the shortcut set up
by cygwin setup.exe on my desktop, not a CMD shell or a DOS "box". My setup
is very standard ("bog ordinary" ;-) for Cygwin and I don't have this sort
of problem building other projects (for example, recently, libpng).

You should also be using Cygwin paths not DOS/Windows device paths, which
> may
> not work with Cygwin tools.
>

In my experience nearly all cygwin tools work with "mixed-mode" pathnames
which are <drive>:/a/path/to/anywhere, the only exception I've become aware
of is GnuPG (gpg).

I'm not sure why the path to the libjpeg-turbo source tree was specified as
a mixed-mode path, I was just in the flow of starting this new effort and
didn't notice that.

> If you want to work in the Windows environment and do Windows builds, try
> Msys2.
>
> --
> Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada
> Thanks Brian, I appreciate your time.

-- Soren

-- 
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

- Raw text -