1538135 - 'can't find custom target thumbv7neon-linux-androideabi', /home/mac/mozilla/mozilla2/third_party/rust/target-lexicon/build.rs:99:5

Status: RESOLVED DUPLICATE of bug 1538419

(Firefox Build System :: General, defect)

Description

[mac198442]

Attachment: Myn .mozconfig

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Tried to build Firefox for android

Actual results:

22:41.06 Compiling target-lexicon v0.2.0
22:41.10 error: failed to run custom build command for target-lexicon v0.2.0
22:41.10 process didn't exit successfully: /home/mac/mozilla/mozilla2/fxand-obj/release/build/target-lexicon-42376ff18ae281f1/build-script-build (exit code: 101)
22:41.10 --- stderr
22:41.10 thread 'main' panicked at 'can't find custom target thumbv7neon-linux-androideabi', /home/mac/mozilla/mozilla2/third_party/rust/target-lexicon/build.rs:99:5

Expected results:

22:41.06 Compiling target-lexicon v0.2.0
Build should have completed normally

Comment 1

[Henri Sivonen (:hsivonen) (temporarily away from Bugzilla)]

Which version of rustc are you building with?

Comment 2

[mac198442]

$ rustc --version
rustc 1.33.0 (2aa4c46cf 2019-02-28)

Comment 3

[Henri Sivonen (:hsivonen) (temporarily away from Bugzilla)]

Does rustup target add thumbv7neon-linux-androideabi remedy the situation?

Comment 4

[mac198442]

No. I already did that. that is how the build get's past the configure state.

I should also give a list of other things I tried that were of no help

1. cargo install cbindgen --force
2. re running mach bootstrap (more on this later)
3. trying later version of the Android NDK
   ( i could not get any version after r15c to get even this far in the build, but that was the same with yesterday's source)
4. trying things from the suggested mozconfig resulting from running mach bootstrap
   commented out the "ac_add_options --target=arm-linux-androideabi" and "ac_add_options --with-android-version=16".
5. Adding the definition of CC and CXX pointing to the .mozbuild version of clang. This actually fixed the issue of not being able to build using NDK r17b using yesterday's source, but still fails the same way with today's source.ac_add_options --with-android-version=16

Comment 5

[mac198442]

opps that (In reply to mac198442 from comment #4)

No. I already did that. that is how the build get's past the configure
state.

I should also give a list of other things I tried that were of no help

1. cargo install cbindgen --force
2. re running mach bootstrap (more on this later)
3. trying later version of the Android NDK
   ( i could not get any version after r15c to get even this far in the
   build, but that was the same with yesterday's source)
4. trying things from the suggested mozconfig resulting from running mach
   bootstrap
   commented out the "ac_add_options --target=arm-linux-androideabi" and
   "ac_add_options --with-android-version=16".
5. Adding the definition of CC and CXX pointing to the .mozbuild version of
   clang. This actually fixed the issue of not being able to build using NDK
   r17b using yesterday's source, but still fails the same way with today's
   source.ac_add_options --with-android-version=16
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Ignore that last part, was a rweult of bad cut-and-paste