Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Print compiler version being used and drop checks for llvm-gcc and old versions of clang

RESOLVED FIXED in mozilla16

Status

()

Core
Build Config
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: espindola, Unassigned)

Tracking

unspecified
mozilla16
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 637974 [details] [diff] [review]
Print compiler version being used and drop checks for llvm-gcc and old versions of clang

We unified the logic for selecting a compiler and rejecting broken ones in MOZ_DEFAULT_COMPILER. In particular, we reject llvm-gcc completely and don't select clang unless the system has a very recent xcode (no gcc 4.2).

This patch then drops old hacks for old versions of clang and llvm-gcc.

It also prints the compiler version to stdout, so that it is recorded on the logs. This is handy as an end to end sanity check now that it is a lot easier to test new compilers on try.
Comment on attachment 637974 [details] [diff] [review]
Print compiler version being used and drop checks for llvm-gcc and old versions of clang

https://tbpl.mozilla.org/?tree=Try&rev=ebc40afd8ca6
Attachment #637974 - Flags: review?(khuey)

Updated

5 years ago
Attachment #637974 - Attachment is patch: true
Comment on attachment 637974 [details] [diff] [review]
Print compiler version being used and drop checks for llvm-gcc and old versions of clang

Review of attachment 637974 [details] [diff] [review]:
-----------------------------------------------------------------

::: configure.in
@@ +1027,5 @@
>  fi # COMPILE_ENVIRONMENT
>  
> +AC_MSG_CHECKING([compiler version])
> +# Just print it so it shows up in the logs.
> +$CC --version

Please use AC_MSG_RESULT, so that this won't show up for people running configure with --quiet.
Attachment #637974 - Flags: review?(khuey) → review+

Comment 3

5 years ago
Rafael: what's the new user experience if the detected Clang is 2.8 or lower? Will configure fail in a later step, or will things fail with a "cryptic" compiler warning during actual build?

It seems to me having an explicit check against the Clang version that prints a clear message ("Clang 2.9 or newer is required") is the most user-friendly thing to do. If we still do that, great. If not, I'm not in favor of removing that detection from configure. But, I'm not a peer, so I'm powerless to stop you.
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=2cd530626b0e

gps, I checked it in as we never select clang when gcc 4.2 is available and it was only dropped on recent versions of xcode.

If you think we should explicitly reject old versions even when the users sets CC, could you please open another bug?
https://hg.mozilla.org/mozilla-central/rev/2cd530626b0e
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
You need to log in before you can comment on or make changes to this bug.