297709 - Don't attempt to use Mac SDKs or compilers that won't work

Status: RESOLVED FIXED

(Firefox Build System :: General, defect)

Description

[Mark Mentovai]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050613 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050613 Firefox/1.0+

The build problems most often reported to me come from people attempting to use
Apple gcc 4.0 build 4061 from Xcode 2.0.  This compiler shipped with Mac OS X
10.4 ("Tiger").  It's broken.  This is bug 280479, but it's also been reported
just about everywhere else.

Since bug 292530, configure prints a non-fatal warning that this compiler won't
work.  That's not high-profile enough.  We can do everyone a favor by stopping
impossible builds right up front.

Also, now that we can support builds using a working gcc 4.0 on the Mac (build
5026 from Xcode 2.1), bug 294244 et seq., there's another impossible build
condition that we should test for at configure time.  gcc 4.0 can only produce
output for 10.3.9 or later.  Earlier SDKs don't include support for the
compiler.  When doing SDK builds, we need to test that the compiler-SDK
combination is valid at configure time and croak with a useful error if it is
not.  This is especially important for Camino, where the standard mozconfig asks
for an SDK that doesn't support the system's default compiler.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Mark Mentovai]

Attachment: configure tests for impossible build conditions

requires autoconf

Comment 2

[Josh Aas]

landed on trunk