Closed
Bug 825151
Opened 12 years ago
Closed 12 years ago
Switch ARMv7 builds over to using NDK r8c
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 20
People
(Reporter: kats, Assigned: kats)
References
Details
Attachments
(1 file, 1 obsolete file)
|
5.76 KB,
patch
|
kats
:
review+
|
Details | Diff | Splinter Review |
As of bug 769099 the new NDK has been deployed to the builders. A try run at https://tbpl.mozilla.org/?tree=Try&rev=71cbe0026b7a shows that switching over the ARMv7 (Android and Android-noion) builds to NDK r8c seems to work well. There is one known issue (bug 824715) which should be fixed soon; once that patch is landed I'd like to land this one as well.
Attachment #696232 -
Flags: review?(ted)
Attachment #696232 -
Flags: review?(blassey.bugs)
|
Assignee | |
Comment 1•12 years ago
|
||
I also notice there's a --with-android-gnu-compiler-version=4.6 option I could use instead of the --with-android-toolchain option, if that's better (I suspect it would be since then we're not hard-coding "linux" into the toolchain path).
|
||
Updated•12 years ago
|
Attachment #696232 -
Flags: review?(ted) → review+
|
|
||
Updated•12 years ago
|
Attachment #696232 -
Flags: review?(blassey.bugs) → review?(ted)
|
||
Updated•12 years ago
|
Attachment #696232 -
Flags: review?(ted) → review+
|
|
Assignee | |
Comment 2•12 years ago
|
||
I update the patch to use --with-android-gnu-compiler-version=4.6 instead (as per https://bugzilla.mozilla.org/show_bug.cgi?id=825453#c2). Carrying r+.
Attachment #696232 -
Attachment is obsolete: true
Attachment #697041 -
Flags: review+
|
|
Assignee | |
Comment 3•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/5c8e41454810
|
||
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/5c8e41454810
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 20
|
||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•