Closed Bug 424890 Opened 13 years ago Closed 13 years ago
mac moz2 builds are not UB: fail to start on 10
.4 or on PPC machines
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
The same behavior is seen in mozilla-central builds, so this is probably a shared bug between the two.
Summary: actionmonkey fails to start on mac. → mozilla-central & actionmonkey fail to start on mac.
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.
Assignee: general → nobody
Product: Core → mozilla.org
QA Contact: general → release
Version: unspecified → other
Summary: mozilla-central & actionmonkey fail to start on mac. → mac moz2 builds are not UB: fail to start on 10.4 or on PPC machines
I'll get this going next week.
Assignee: nobody → bhearsum
Priority: -- → P3
Right, this is the manifestation of bug 423672 when using the 10.5 SDK.
Er, this is actually bug 423691, you mentioned the other failure mode in the other bug.
Priority: P3 → P2
Whiteboard: [waiting on review]
Comment on attachment 311554 [details] [diff] [review] [checked in] enable universal builds changeset: 11:b7f5d88c1bfa tag: tip user: Ben Hearsum <firstname.lastname@example.org> date: Tue Mar 25 09:16:57 2008 -0400 files: mozilla2/macosx/mozconfig
Attachment #311554 - Attachment description: enable universal builds → [checked in] enable universal builds
I just triggered a mozilla-central dep build, we should see results shortly.
These ended up failing out, see bugs 425003 and 425005. Going to --disable-tests to work around the actionmonkey failure.
My mistake, --disable-tests is to work around the *mozilla-central* build.
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.
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.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Release Engineering: Talos → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.