unofficial mirror
 help / color / mirror / code / Atom feed
From: "Måns Rullgård" <>
To: Jan Stary <>
Subject: Re: compiler detection
Date: Sat, 22 Aug 2020 22:11:22 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Jan Stary's message of "Sat, 22 Aug 2020 22:42:03 +0200")

Jan Stary <> writes:

> It seems ./configure is confused about which compiler it found.
> When run without arguments, ./configure will look for (and find) gcc,
> without ever bothering to look for cc.
> With CC specified, using either of
> 	./configure CC=cc
> 	env CC=cc ./configure
> this is what happens:
> checking for gcc... cc
> 	$ cc --version
> 	OpenBSD clang version 10.0.1 
> 	Target: amd64-unknown-openbsd6.7
> 	Thread model: posix
> 	InstalledDir: /usr/bin
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> 	no
> I don't know what effect it has on the subsequent compilation,
> or what assumptions thinking "we are using the GNU compiler" leads to.

That checks whether __GNUC__ is defined.  Since clang supports (most)
gcc extensions, it defines this symbol.

Måns Rullgård

SoX-devel mailing list

      reply	other threads:[~2020-08-22 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 20:42 compiler detection Jan Stary
2020-08-22 21:11 ` Måns Rullgård [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).