424890 - mac moz2 builds are not UB: fail to start on 10.4 or on PPC machines

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[alice nodelman [:alice] [:anode]]

I see the following errors and the browser doesn't open:

dyld: lazy symbol binding failed: Symbol not found: _pthread_mutexattr_destroy$UNIX2003
  Referenced from: ../Minefield.app/Contents/MacOS/libsqlite3.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _pthread_mutexattr_destroy$UNIX2003
  Referenced from: ../Minefield.app/Contents/MacOS/libsqlite3.dylib
  Expected in: /usr/lib/libSystem.B.dylib

Comment 1

[alice nodelman [:alice] [:anode]]

The same behavior is seen in mozilla-central builds, so this is probably a shared bug between the two.

Comment 2

[Benjamin Smedberg]

I believe that this is due to the moz2 build machine not specifying an SDK in the mozconfig (nor doing universal builds, which specify an SDK internally). Punting back to build, because these builds should be UB.

Comment 3

[[e-mail] (:bhearsum)]

I'll get this going next week.

Comment 4

[(not currently active) Ted Mielczarek]

Right, this is the manifestation of bug 423672 when using the 10.5 SDK.

Comment 5

[(not currently active) Ted Mielczarek]

Er, this is actually bug 423691, you mentioned the other failure mode in the other bug.

Comment 6

[[e-mail] (:bhearsum)]

Attachment: [checked in] enable universal builds

Comment 7

[[e-mail] (:bhearsum)]

Comment on attachment 311554 [details] [diff] [review]
[checked in] enable universal builds

changeset:   11:b7f5d88c1bfa
tag:         tip
user:        Ben Hearsum <[e-mail]>
date:        Tue Mar 25 09:16:57 2008 -0400
files:       mozilla2/macosx/mozconfig

Comment 8

[[e-mail] (:bhearsum)]

I just triggered a mozilla-central dep build, we should see results shortly.

Comment 9

[[e-mail] (:bhearsum)]

These ended up failing out, see bugs 425003 and 425005. Going to --disable-tests to work around the actionmonkey failure.

Comment 10

[[e-mail] (:bhearsum)]

My mistake, --disable-tests is to work around the *mozilla-central* build.

Comment 11

[[e-mail] (:bhearsum)]

Builds are working now, packaging is failing because 'make package' is being run in the wrong directory. There's a patch up in bug 425003 to fix it.

Comment 12

[[e-mail] (:bhearsum)]

Alright. With bug 425003 fixed I tested a package on a 10.4 PPC machine: it ran fine. Can't test actionmonkey because of bug 425005 but I suspect it will be just fine.