If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Disallow builds with clang < 3.2

NEW
Unassigned

Status

()

Core
Build Config
4 years ago
4 years ago

People

(Reporter: Ehsan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

Clang 3.2 is the lowest version of clang which we need to support building with.

Comment 1

4 years ago
So I'm guessing this refers to the llvm.org version of clang?  The XCode version is labeled 4.2 and what was labeled 4.0 doesn't compile trunk at this point.

Comment 2

4 years ago
(In reply to John Daggett (:jtd) from comment #1)
> So I'm guessing this refers to the llvm.org version of clang?  The XCode
> version is labeled 4.2 and what was labeled 4.0 doesn't compile trunk at
> this point.

The current xcode version is labeled 4.2.

The previous one, which is still installed on many systems, was labeled 4.1. Like 4.0, it cannot compile trunk. However, the error message is pretty obtuse (it complains about a missing operator=() on JS::Value, which is patently nonsense, since the compiler should create one). This leads to confused developers and new bugs.

The subject matter of *this* bug is to provide a clear message to developers that the compiler is explicitly not supported, rather than simply generating inexplicable error messages.
Created attachment 792570 [details]
build failure with Apple/clang-421.11.66

I can't compile with this either:
Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

Updated

4 years ago
Blocks: 904108
(In reply to comment #1)
> So I'm guessing this refers to the llvm.org version of clang?  The XCode
> version is labeled 4.2 and what was labeled 4.0 doesn't compile trunk at this
> point.

I was talking about any clang release based on llvm.org revisions older than 3.2.  That includes LLVM Clang 3.1 and below, and Apple Clang 4.1 and below.  Note that the Apple version of the clang is based off of a private repository with custom fixes on top of the llvm.org code, and they don't follow the LLVM release numbers to make life miserable for everybody on the planet ;-)
You need to log in before you can comment on or make changes to this bug.