842537 - No Mac OS X l10n builds for -aurora and -central

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect)

Description

[Frank Wein [:mcsmurf]]

It looks like no localized Mac builds get built currently. 

Error messages in comm-central Mac build log (l10n):
checking host system type... x86_64-apple-darwin11.2.0
checking target system type... x86_64-apple-darwin11.2.0
checking build system type... x86_64-apple-darwin11.2.0
checking for mawk... (cached) awk
checking for python2.7... (cached) /tools/python/bin/python2.7
Creating Python environment
checking Python environment is Mozilla virtualenv... yes
checking for perl5... (cached) /usr/bin/perl
checking for gcc... (cached) ./clang/bin/clang
checking whether the C compiler (./clang/bin/clang -gdwarf-2 ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
configure: error: ./configure failed for mozilla

Build log from comm-aurora Mac build log (l10n de):
running /bin/sh ./configure  --with-macos-sdk=/Developer/SDKs/MacOSX10.6.sdk --with-ccache --enable-application=suite --with-l10n-base=../../l10n-central --enable-update-channel=aurora --enable-update-packaging --disable-install-strip --enable-debug-symbols=-gdwarf-2 --enable-application=suite --with-l10n-base=../releases/l10n/mozilla-aurora --enable-update-packaging --enable-application=../suite --disable-official-branding --with-branding=../suite/branding/nightly --with-l10n-base=/builds/slave/c-aurora-osx64-l10n-ntly/build/releases/l10n/mozilla-aurora --cache-file=.././config.cache --srcdir=.
Adding configure options from /builds/slave/c-aurora-osx64-l10n-ntly/build/comm-aurora/./.mozconfig:
  --with-macos-sdk=/Developer/SDKs/MacOSX10.6.sdk
  --with-ccache
  --enable-application=suite
  --with-l10n-base=../../l10n-central
  --enable-update-channel=aurora
  --enable-update-packaging
  --disable-install-strip
  --enable-debug-symbols=-gdwarf-2
loading cache .././config.cache
checking host system type... x86_64-apple-darwin11.2.0
checking target system type... x86_64-apple-darwin11.2.0
checking build system type... x86_64-apple-darwin11.2.0
checking for mawk... (cached) awk
checking for python2.7... (cached) /tools/python/bin/python2.7
Creating Python environment
checking for perl5... (cached) /usr/bin/perl
checking for gcc... (cached) ./mozilla/../clang/bin/clang
checking whether the C compiler (./mozilla/../clang/bin/clang -gdwarf-2 ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.

Comment 1

[Frank Wein [:mcsmurf]]

For comparison build log from working comm-central Mac OS X trunk build:
Adding configure options from /builds/slave/c-cen-t-osx64-dbg/build/.mozconfig:
  --with-ccache
  --enable-debug
  --enable-application=suite
  --enable-tests
  --enable-trace-malloc
  --enable-debug-symbols=-gdwarf-2
loading cache .././config.cache
checking host system type... x86_64-apple-darwin11.2.0
checking target system type... x86_64-apple-darwin11.2.0
checking build system type... x86_64-apple-darwin11.2.0
checking for mawk... (cached) awk
checking for python2.7... (cached) /tools/python/bin/python2.7
Creating Python environment
checking Python environment is Mozilla virtualenv... yes
checking for perl5... (cached) /usr/bin/perl
checking for gcc... (cached) /builds/slave/c-cen-t-osx64-dbg/build/clang/bin/clang
checking whether the C compiler (/builds/slave/c-cen-t-osx64-dbg/build/clang/bin/clang  ) works... yes

Comment 2

[Frank Wein [:mcsmurf]]

Looks like this bug has been "caused" by re-using the config.status file for mozilla/, not sure why this worked fine before some time in the past, maybe because mozconfig was different back then:
=== Output ===
sh -- ./configure --enable-application=suite --with-l10n-base=../releases/l10n/mozilla-aurora --enable-update-packaging
[...]
checking whether the C compiler (./mozilla/../clang/bin/clang -gdwarf-2 ) works... yes
checking whether the C compiler (./mozilla/../clang/bin/clang -gdwarf-2 ) is a cross-compiler... no
[...]
configuring in mozilla
running /bin/sh ./configure  --with-macos-sdk=/Developer/SDKs/MacOSX10.6.sdk --with-ccache --enable-application=suite --with-l10n-base=../../l10n-central --enable-update-channel=aurora --enable-update-packaging --disable-install-strip --enable-debug-symbols=-gdwarf-2 --enable-application=suite --with-l10n-base=../releases/l10n/mozilla-aurora --enable-update-packaging --enable-application=../suite --disable-official-branding --with-branding=../suite/branding/nightly --with-l10n-base=/builds/slave/comm-aurora-osx64-l10n-ntly/build/releases/l10n/mozilla-aurora --cache-file=.././config.cache --srcdir=.
[...]
checking whether the C compiler (./mozilla/../clang/bin/clang -gdwarf-2 ) works... no

So (as far as I see it) it's looking in the wrong folder for the clang compiler.

Comment 3

[Justin Wood (:Callek)]

Attachment: [custom] part 1

So apparantly moco TB l10n builders are exactly like ours, except they don't do tooltool on the l10n.

I suspect dropping tooltool here may come back and bite us in the future, but at least it will bite us the same as TB and we can be fine for now.

Comment 4

[Justin Wood (:Callek)]

Attachment: [configs] fix it

Same but for the release builders.

---

I should note I tested the custom change manually on the master, and it does indeed cause us to get past configure!

Comment 5

[Frank Wein [:mcsmurf]]

Looks like the change works, but one thing might need to be fixed in the future: It uses gcc instead of clang. A few files get compiled during the l10n step (maybe for the updater? not sure).

Comment 6

[Justin Wood (:Callek)]

yea that was my "might bite us later" comment. But nothing compiled during 10n is shipped, its purely for the update stuff.