Closed Bug 860235 Opened 7 years ago Closed 7 years ago
.i686 and libstdc++.i686 in the android test mock environment
bug 859705 requires to run a binary that is result of the android build on the android test mock environment. Since the build environment is 32-bits, the binary is 32-bits, while the android test mock environment, aiui is 64-bits. Which leads that binary to fail to execute because its dependencies are not all there: Running ldd /builds/tegra-314/test/build/tests/bin/host/szip linux-gate.so.1 => (0x008c0000) libz.so.1 => not found libstdc++.so.6 => not found libm.so.6 => /lib/libm.so.6 (0x004bd000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00a50000) libc.so.6 => /lib/libc.so.6 (0x00110000) /lib/ld-linux.so.2 (0x00404000) Thus, please install the two missing libraries, zlib.i686 and libstdc++.i686
found in triage.
Component: Release Engineering → Release Engineering: Platform Support
QA Contact: coop
So, I'm not really a fan of throwing packages in this manifest, but I can't even come up with a valid package module name for this stuff, in a way I could have the foopy install it properly. I'm open to suggestions on how to do this differently as well.
Attachment #736169 - Flags: review?(rail)
Comment on attachment 736169 [details] [diff] [review] [puppet] v1 packages::ia32libs is exactly what you want ;)
Attachment #736169 - Flags: review?(rail) → review-
As we all discussed in IRC yesterday, this is the plan as rail suggested it. concerns raised were: * (dustin raised:) possible mis-match of the .i686 libc with what the x86 mock is using, since the x64 repo snapshot is a few months newer than the x86 snapshot. ** Obviated by glandiums assertion that it is fine this way. * (callek raised:) ia32libs module not being suitable for these inserts ** dustin and rail both think it is fair to use it, since it is for basic x86 needs on x64 machines. If we needed a wider swatch of libs we could/would use a different module/impl but this is cleanest for our needs now.
Comment on attachment 736981 [details] [diff] [review] [puppet] v2 Ship it!
Attachment #736981 - Flags: review?(rail) → review+
https://hg.mozilla.org/build/puppet/rev/4b4ec8f835f8 Should take no more than 15-20 minutes to fully deploy the way we have puppet setup on these machines.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
I backed this out on friday -- forgot to comment/reopen. We broke stuff, I'll attempt relanding when I have a clear head.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
relanded: https://hg.mozilla.org/build/puppet/rev/637816f3c008 and the foopy init.pp as well :( https://hg.mozilla.org/build/puppet/rev/5ab0f346e8e7
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 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.