arm-linux-androideabi-gcc: internal compiler error: Killed (program cc1plus) #7723
Labels
stat:awaiting response
Status - Awaiting response from author
Comments
|
This seems similar to tensorflow/serving#97, probably due to some interaction with Docker. Can you try adding |
poxvoculi
added
the
stat:awaiting response
|
Also, are both of the laptops you tried this on running osx? |
|
They are both OS X, one is El Capitan, one is Sierra (I updated the description to record the details). If you can point me at Docker container which supports building the TensorFlow Android demo, then I can try using that. I couldn't find one when I searched online. I added the |
|
Can you ensure that you have enough memory available in your docker environment? This seems like a common issue: https://groups.google.com/a/tensorflow.org/forum/#!topic/discuss/zjwDXhD6k1w |
poxvoculi
added
the
stat:awaiting response
|
Awesome, adding Full output: |
hongxu-jia
added a commit
to hongxu-jia/meta-tensorflow
that referenced
this issue
Apr 21, 2020
There is gcc Killed failure: ... |tmp-glibc/work/corei7-32-wrsmllib32-linux/lib32-tensorflow/ 1.13.0-r0/git/tensorflow/core/kernels/BUILD:3158:1: C++ compilation of rule '//tensorflow/core/kernels:cwise_op' failed (Killed): gcc failed: error executing command ... From Bazel User Manual --local_resources availableRAM,availableCPU,availableIO This option, which takes three comma-separated floating point arguments, specifies the amount of local resources that Bazel can take into consideration when scheduling build and test activities. Option expects amount of available RAM (in MB), number of CPU cores (with 1.0 representing single full core) and workstation I/O capability (with 1.0 representing average workstation). [1] According to [2][3], explicitly set the amount of local host RAM 4096 MB available to Bazel, the number of local CPU 4 cores available to Bazel, the number of jobs is 4 which should be executed concurrently. Refer: [1] https://stackoverflow.com/questions/34756370/is-there-a-way-to-limit-the-number-of-cpu-cores-bazel-uses [2] tensorflow/tensorflow#7723 [3] tensorflow/tensorflow#24318 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
hongxu-jia
added a commit
to hongxu-jia/meta-tensorflow
that referenced
this issue
Apr 21, 2020
There is gcc Killed failure: ... |tmp-glibc/work/corei7-32-wrsmllib32-linux/lib32-tensorflow/ 1.13.0-r0/git/tensorflow/core/kernels/BUILD:3158:1: C++ compilation of rule '//tensorflow/core/kernels:cwise_op' failed (Killed): gcc failed: error executing command ... From Bazel User Manual --local_resources availableRAM,availableCPU,availableIO This option, which takes three comma-separated floating point arguments, specifies the amount of local resources that Bazel can take into consideration when scheduling build and test activities. Option expects amount of available RAM (in MB), number of CPU cores (with 1.0 representing single full core) and workstation I/O capability (with 1.0 representing average workstation). [1] According to [2][3], explicitly set the amount of local host RAM 4096 MB available to Bazel, the number of local CPU 4 cores available to Bazel, the number of jobs is 4 which should be executed concurrently. Refer: [1] https://stackoverflow.com/questions/34756370/is-there-a-way-to-limit-the-number-of-cpu-cores-bazel-uses [2] tensorflow/tensorflow#7723 [3] tensorflow/tensorflow#24318 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this issue
May 22, 2024
…res Bazel uses There is gcc Killed failure: ... |tmp-glibc/work/corei7-32-wrsmllib32-linux/lib32-tensorflow/ 1.13.0-r0/git/tensorflow/core/kernels/BUILD:3158:1: C++ compilation of rule '//tensorflow/core/kernels:cwise_op' failed (Killed): gcc failed: error executing command ... From Bazel User Manual --local_resources availableRAM,availableCPU,availableIO This option, which takes three comma-separated floating point arguments, specifies the amount of local resources that Bazel can take into consideration when scheduling build and test activities. Option expects amount of available RAM (in MB), number of CPU cores (with 1.0 representing single full core) and workstation I/O capability (with 1.0 representing average workstation). [1] According to [2][3], explicitly set the amount of local host RAM 4096 MB available to Bazel, the number of local CPU 4 cores available to Bazel, the number of jobs is 4 which should be executed concurrently. Refer: [1] https://stackoverflow.com/questions/34756370/is-there-a-way-to-limit-the-number-of-cpu-cores-bazel-uses [2] tensorflow/tensorflow#7723 [3] tensorflow/tensorflow#24318 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
daregit
pushed a commit
to daregit/yocto-combined
that referenced
this issue
May 22, 2024
…res Bazel uses There is gcc Killed failure: ... |tmp-glibc/work/corei7-32-wrsmllib32-linux/lib32-tensorflow/ 1.13.0-r0/git/tensorflow/core/kernels/BUILD:3158:1: C++ compilation of rule '//tensorflow/core/kernels:cwise_op' failed (Killed): gcc failed: error executing command ... From Bazel User Manual --local_resources availableRAM,availableCPU,availableIO This option, which takes three comma-separated floating point arguments, specifies the amount of local resources that Bazel can take into consideration when scheduling build and test activities. Option expects amount of available RAM (in MB), number of CPU cores (with 1.0 representing single full core) and workstation I/O capability (with 1.0 representing average workstation). [1] According to [2][3], explicitly set the amount of local host RAM 4096 MB available to Bazel, the number of local CPU 4 cores available to Bazel, the number of jobs is 4 which should be executed concurrently. Refer: [1] https://stackoverflow.com/questions/34756370/is-there-a-way-to-limit-the-number-of-cpu-cores-bazel-uses [2] tensorflow/tensorflow#7723 [3] tensorflow/tensorflow#24318 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to create a Docker image which has all the dependencies required to build the TensorFlow Android demo app from source (including the Android SDK, NDK and build tools).
I'm simply starting with
gcr.io/tensorflow/tensorflow:latest-develand then adding the Android dependencies on top. This lists all the steps I've done so far:https://medium.com/@daj/docker-image-for-building-tensorflow-android-demo-app-97c98ce37d9e#.y0kwcx63j
Unfortunately I keep hitting this error:
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
These GitHub issues had similar titles, but the details looked a bit different:
https://github.com/tensorflow/tensorflow/issues?q=is%3Aissue+BadExitStatusException+Process+exited+with+status+4++cc1plus+is%3Aopen
Environment info
Operating System: Docker version 1.13.1, build 092cba3 (running inside Mac OS X, I tried on both El Capitan and Sierra with the same results)
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
I've pushed my Docker image (after hitting the build error) to a public location, so you should be able to pull it and then run the build:
What other attempted solutions have you tried?
Logs or other output that would be helpful
Normal build (without the
--verbose_failuresoption - scroll down for the--verbose_failures, I've included that too):Here's the result with the
--verbose_failuresoption set:The text was updated successfully, but these errors were encountered: