GNU bug report logs - #21336
configure fails to detect C++ compiler on case-insensitive FS

Previous Next

Package: automake;

Reported by: "Daniel Macks" <dmacks <at> netspace.org>

Date: Mon, 24 Aug 2015 10:13:02 UTC

Severity: normal

Tags: confirmed

Done: Karl Berry <karl <at> freefriends.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: "Daniel Macks" <dmacks <at> netspace.org>
Subject: bug#21336: closed (Re: [PATCH] configure: handle KCC on
 case-insensitive filesystems)
Date: Mon, 13 Dec 2021 02:09:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#21336: configure fails to detect C++ compiler on case-insensitive FS

which was filed against the automake package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 21336 <at> debbugs.gnu.org.

-- 
21336: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21336
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Karl Berry <karl <at> freefriends.org>
To: vapier <at> gentoo.org
Cc: 21336 <at> debbugs.gnu.org, automake-patches <at> gnu.org
Subject: Re: [PATCH] configure: handle KCC on case-insensitive filesystems
Date: Sun, 12 Dec 2021 19:08:52 -0700
    Subject: [PATCH] configure: handle KCC on case-insensitive filesystems

Pushed with doc tweak per Jim. Thanks.

[Message part 3 (message/rfc822, inline)]
From: "Daniel Macks" <dmacks <at> netspace.org>
To: bug-automake <at> gnu.org
Subject: configure fails to detect C++ compiler on case-insensitive FS
Date: Mon, 24 Aug 2015 06:12:32 -0400
Building automake-1.15 on OS X 10.10 on a case-insensitive filesystem, during ./configure I see:

checking whether cc understands -c and -o together... yes
checking for aCC... no
checking for FCC... no
checking for KCC... KCC
checking whether the C++ compiler works... no
configure: WARNING: C++ compiler cannot create executables
configure: tests requiring the C++ compiler will be skipped

I don't have "KCC" and my C++ compiler (at "c++" or "g++") is fine. I do however have /usr/bin/kcc, which AC_PROG_CXX finds when it looks for "KCC" on my filesystem:

# The list of C++ compilers here has been copied, pasted and edited
# from 'lib/autoconf/c.m4:AC_PROG_CXX' in the Autoconf distribution.
# Keep it in sync, or better again, find out a way to avoid this code
# duplication.
_AM_COMPILER_CAN_FAIL([AC_PROG_CXX(dnl
  [aCC $am_CC FCC KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++])],
  [CXX=false; _AM_SKIP_COMP_TESTS([C++])])

But my "kcc" is some completely unrelated kerberos tool, so when AC_PROG_CXX tests to see whether it behaves as a compiler, it fails because it isn't a compiler, and the autoconf tests don't get as far as my actual compiler in the list of possibilities. This is the same situation as the now-fixed automake bugs #11893 and #10766, where looking for "CC" was finding "cc" on case-insensitive filesystems, so presumably the same solution could work. That is, only look for "KCC" if it's a case-sensitive FS.

This code from which this block is documented to derive is:

[g++ c++ gpp aCC CC cxx cc++ cl.exe FCC KCC RCC xlC_r xlC]

in autoconf git, so an alternate solution is to re-sync with that (notably, "KCC" is well after "c++" and "g++").

dan

--
Daniel Macks
dmacks <at> netspace.org



This bug report was last modified 3 years and 165 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.