From: nobu@... Date: 2018-03-09T01:28:07+00:00 Subject: [ruby-core:86061] [Ruby trunk Bug#14590][Closed] Why is config script checking for g++ Issue #14590 has been updated by nobu (Nobuyoshi Nakada). Status changed from Open to Closed Some extension libraries, e.g., ones using swig, need a C++ compiler. ---------------------------------------- Bug #14590: Why is config script checking for g++ https://bugs.ruby-lang.org/issues/14590#change-70925 * Author: vo.x (Vit Ondruch) * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- I am wondering what is the reason the configuration scripts are checking for availability of g++? ~~~ checking for x86_64-redhat-linux-gnu-g++... no checking for x86_64-redhat-linux-gnu-c++... no checking for x86_64-redhat-linux-gnu-gpp... no checking for x86_64-redhat-linux-gnu-aCC... no checking for x86_64-redhat-linux-gnu-CC... no checking for x86_64-redhat-linux-gnu-cxx... no checking for x86_64-redhat-linux-gnu-cc++... no checking for x86_64-redhat-linux-gnu-cl.exe... no checking for x86_64-redhat-linux-gnu-FCC... no checking for x86_64-redhat-linux-gnu-KCC... no checking for x86_64-redhat-linux-gnu-RCC... no checking for x86_64-redhat-linux-gnu-xlC_r... no checking for x86_64-redhat-linux-gnu-xlC... no checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes ~~~ introduced in r8371. g++ is not needed for compilation, is it? Or is it needed on some platforms? -- https://bugs.ruby-lang.org/ Unsubscribe: