Closed Bug 748448 Opened 13 years ago Closed 13 years ago

Need sources/android/cpufeatures from the NDK

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

All
Gonk (Firefox OS)
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: derf, Assigned: derf)

References

Details

Attachments

(2 files, 2 obsolete files)

libvpx v1.0.0 (see bug 730907) uses Android's cpufeatures library to detect ARM processor features. This "library" is only provided as source code with the NDK, and must be manually compiled into the application, but the source files are not installed on the builder. Note that in old NDKs (r4) this was distributed as sources/cpufeatures instead of sources/android/cpufeatures.
Blocks: 730907
If this is something that should be added to the toolchain, please build the toolchain and upload it to people. From there, I'll put the file onto our fileserver and we can prepare the manifest changes that are needed to set up the new toolchain.
Assignee: nobody → tterribe
I think this patch is all that's needed to add the right thing to the toolchain. I don't know much about how the B2G development process works. What do I need to do to get that reviewed and landed?
r=me, Landed in github repo. https://github.com/andreasgal/B2G/commit/2b3af23df1ac0b673e3a4bf7f92753bace1b0e1e Will mark as resolved once we've finished the toolchain pushing process.
Attached file gonk-toolchain-1 manifest (obsolete) (deleted) —
I renamed the toolchain file provided to me to gonk-toolchain-1.tar.bz2, since this is no longer toolchain 0. This manifest file should be checked into your code at the following location to test using this new toolchain: b2g/config/tooltool-manifests/releng.manifest I'd suggest pushing this to try first, especially since this is our first b2g toolchain update. In the build log, you should search for gonk-toolchain-1 to ensure that the correct tarball is being used. At some point, the process of uploading the toolchain snapshots will be automated by using an http form or something like that and this will just be generating a manifest.
Try pushed to https://tbpl.mozilla.org/?tree=Try&rev=1103a64ddf7e Assuming this succeeds, will land the new manifest and close out.
Attached file new releng.manifest (obsolete) (deleted) —
this manifest refers to the correct tarball that has been repacked
Attachment #618375 - Attachment is obsolete: true
Attached file new toolchain (deleted) —
changes were needed to the toolchain. here is a new manifest file
Attachment #618439 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: