Those are different symptoms (and also not the same error) - the message is different.
You can try this: cd build/soong; git status; git diff; git log -1 That will tell you if anything has been changed. You can also look at that line of that file (build/soong/cc/config/x86_darwin_host.go , line 91) and inspect whether it seems to be valid On Monday, October 2, 2017 at 8:41:11 AM UTC-7, aadi wrote: > > Hello again but i am facing the same issue again : > > > FAILED: out/soong/.bootstrap/soong-cc-config/test/android/soong/cc/config.a > > > GOROOT='./prebuilts/go/darwin-x86' > ./prebuilts/go/darwin-x86/pkg/tool/darwin_amd64/compile -o > out/soong/.bootstrap/soong-cc-config/test/android/soong/cc/config.a -p > android/soong/cc/config -complete -I > out/soong/.bootstrap/blueprint-parser/pkg -I > out/soong/.bootstrap/blueprint-deptools/pkg -I > out/soong/.bootstrap/blueprint-pathtools/pkg -I > out/soong/.bootstrap/blueprint-proptools/pkg -I > out/soong/.bootstrap/blueprint/pkg -I > out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg -I > out/soong/.bootstrap/blueprint-bootstrap/pkg -I > out/soong/.bootstrap/soong/pkg -I out/soong/.bootstrap/soong-env/pkg -I > out/soong/.bootstrap/soong-android/pkg -pack build/soong/cc/config/clang.go > build/soong/cc/config/global.go build/soong/cc/config/tidy.go > build/soong/cc/config/toolchain.go build/soong/cc/config/arm_device.go > build/soong/cc/config/arm64_device.go build/soong/cc/config/mips_device.go > build/soong/cc/config/mips64_device.go build/soong/cc/config/x86_device.go > build/soong/cc/config/x86_64_device.go > build/soong/cc/config/x86_darwin_host.go > build/soong/cc/config/x86_linux_host.go > build/soong/cc/config/x86_linux_bionic_host.go > build/soong/cc/config/x86_windows_host.go build/soong/cc/config/tidy_test.go > > build/soong/cc/config/x86_darwin_host.go:91: syntax error: unexpected > semicolon or newline, expecting comma or } > > [15/40] compile > out/soong/.bootstrap/soong-cc-config/pkg/android/soong/cc/config.a > > FAILED: out/soong/.bootstrap/soong-cc-config/pkg/android/soong/cc/config.a > > > GOROOT='./prebuilts/go/darwin-x86' > ./prebuilts/go/darwin-x86/pkg/tool/darwin_amd64/compile -o > out/soong/.bootstrap/soong-cc-config/pkg/android/soong/cc/config.a -p > android/soong/cc/config -complete -I > out/soong/.bootstrap/blueprint-parser/pkg -I > out/soong/.bootstrap/blueprint-deptools/pkg -I > out/soong/.bootstrap/blueprint-pathtools/pkg -I > out/soong/.bootstrap/blueprint-proptools/pkg -I > out/soong/.bootstrap/blueprint/pkg -I > out/soong/.bootstrap/blueprint-bootstrap-bpdoc/pkg -I > out/soong/.bootstrap/blueprint-bootstrap/pkg -I > out/soong/.bootstrap/soong/pkg -I out/soong/.bootstrap/soong-env/pkg -I > out/soong/.bootstrap/soong-android/pkg -pack build/soong/cc/config/clang.go > build/soong/cc/config/global.go build/soong/cc/config/tidy.go > build/soong/cc/config/toolchain.go build/soong/cc/config/arm_device.go > build/soong/cc/config/arm64_device.go build/soong/cc/config/mips_device.go > build/soong/cc/config/mips64_device.go build/soong/cc/config/x86_device.go > build/soong/cc/config/x86_64_device.go > build/soong/cc/config/x86_darwin_host.go > build/soong/cc/config/x86_linux_host.go > build/soong/cc/config/x86_linux_bionic_host.go > build/soong/cc/config/x86_windows_host.go > > build/soong/cc/config/x86_darwin_host.go:91: syntax error: unexpected > semicolon or newline, expecting comma or } > > [18/40] compile > out/soong/.bootstrap/soong-genrule/pkg/android/soong/genrule.a > > ninja: build stopped: subcommand failed. > > 08:54:31 soong bootstrap failed with: exit status 1 > > make: *** [run_soong_ui] Error 1 > > > > > Please need help. > > > On Saturday, September 9, 2017 at 1:44:19 AM UTC+5:30, > [email protected] wrote: >> >> You can check how many files are currently open before running the >> Android build to see if that's the cause. You can check that by doing >> >> lsof | wc -l >> >> You could also run this to clarify under which circumstances it fails: >> >> rm -f /tmp/log >> echo starting test | tee -a /tmp/log >> echo initial number of previously open files in system: `lsof | wc -l` | >> tee -a /tmp/log >> make -j8 nothing && echo make nothing with existing state succeeded | tee >> -a /tmp/log >> rm -rf out && make -j8 nothing && echo make nothing with empty out >> succeeded | tee -a /tmp/log >> make -j8 nothing && echo second make nothing succeeded | tee -a /tmp/log >> make -j8 && echo full make succeeded | tee -a /tmp/log >> make -j8 && echo second full make succeeded | tee -a /tmp/log >> echo test complete | tee -a /tmp/log >> echo results are >> cat /tmp/log >> >> My guess is that even `rm -rf out && make -j nothing` fails, but the >> above should clarify. >> >> Unfortunately enabling ota_tools isn't going to work on its own because >> it depends on some things that aren't supported on Mac. That's probably >> sufficiently unrelated to warrant a new discussion thread at least. You'll >> probably want to elaborate on what you'd like it for. >> >> On Friday, September 8, 2017 at 8:30:11 AM UTC-7, aadi wrote: >>> >>> I deleted everything and reinstalled my Mac and re synced everything >>> >>> >>> Now when I run - mv out/.module_paths /tmp && make -j8 nothing && make >>> -j8 nothing && make -j8 >>> >>> >>> It says : >>> >>> mv: rename out/.module_paths to /tmp/.module_paths: No such file or >>> directory >>> >>> >>> And repo status -j8 shows : >>> >>> >>> adityas-Mac-Pro:android aditya$ repo status -j8 >>> >>> *project build/make/ *(*** NO BRANCH ***) >>> >>> -- .DS_Store >>> >>> >>> And yes I previously changed build_ota_package := false to true >>> >>> >>> My lunch command was asp_arm_eng >>> >>> >>> >>> On Thursday, September 7, 2017 at 2:38:10 AM UTC+5:30, >>> [email protected] wrote: >>>> >>>> Hmm it hasn’t failed yet on my system so I’ll need some more help >>>> reproducing it. >>>> >>>> >>>> When you run >>>> >>>> mv out/.module_paths /tmp && make -j8 nothing && make -j8 nothing && >>>> make -j8 >>>> >>>> >>>> , does it do any successful builds, or is it the first `make -j8 >>>> nothing` that fails? >>>> >>>> >>>> Some more things we can double check: >>>> >>>> >>>> What does `repo status -j8` say - does it indicate any changes? >>>> >>>> Also, if you do >>>> >>>> >>>> cd .repo/manifests && git status >>>> >>>> >>>> which version does it give? For me it gives >>>> 31babfb21d81098c3c3e60008074db7aef8b91f3 >>>> >>>> >>>> For the part about the otatools, did you do anything special to enable >>>> it? >>>> >>>> Inside build/core/Makefile , there is some text that says >>>> >>>> >>>> ifeq ($(BUILD_OS),darwin) >>>> >>>> build_ota_package := false >>>> >>>> endif >>>> >>>> >>>> so on a Mac the error is supposed to be >>>> >>>> >>>> ninja: error: unknown target 'otatools', did you mean 'tools'? >>>> >>>> 13:58:34 ninja failed with: exit status >>>> >>>> >>>> What was your lunch command (for example `lunch aosp_arm-eng`)? >>>> >>>> On Wednesday, September 6, 2017 at 10:08:56 AM UTC-7, aadi wrote: >>>>> >>>>> when i run the command mv out/.module_paths /tmp && make -j8 nothing >>>>> && make -j8 nothing && make -j8 >>>>> >>>>> same error comes on the screen >>>>> >>>>> and i did >>>>> >>>>> hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size >>>>> 150g ~/android.dmg && hdiutil attach ~/android.dmg -mountpoint >>>>> /Volumes/android >>>>> >>>>> >>>>> and when i run make -j8 otatools it shows me error : >>>>> >>>>> >>>>> ninja: error: 'out/host/darwin-x86/bin/make_f2fs', needed by >>>>> 'otatools', missing and no known rule to make it >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Wednesday, September 6, 2017 at 12:12:50 AM UTC+5:30, >>>>> [email protected] wrote: >>>>>> >>>>>> Hey thanks for reporting this. >>>>>> >>>>>> >>>>>> I’ll see if I can reproduce it. What did you do for setting up a >>>>>> case-sensitive filesystem on the Mac - was it >>>>>> >>>>>> >>>>>> hdiutil create -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size >>>>>> 40g ~/android.dmg && hdiutil attach ~/android.dmg -mountpoint >>>>>> /Volumes/android >>>>>> >>>>>> >>>>>> (from https://source.android.com/source/initializing )? >>>>>> >>>>>> >>>>>> Also, what happens if you run: >>>>>> >>>>>> >>>>>> mv out/.module_paths /tmp && make -j8 nothing && make -j8 nothing && >>>>>> make -j8 >>>>>> >>>>>> >>>>>> ? >>>>>> >>>>>> On Tuesday, September 5, 2017 at 8:40:47 AM UTC-7, aadi wrote: >>>>>>> >>>>>>> When ever i run make -j8 the following error comes up. >>>>>>> >>>>>>> I'm running mac os x sierra 10.12.6 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 12:49:43 Could not create module-finder: finder encountered 609 >>>>>>> errors: >>>>>>> [/Volumes/android/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9/lib/gcc/x86_64-linux-android/4.9.x/include: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9/lib/gcc/x86_64-linux-android/4.9.x/include/omp.h: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/lib/gcc/x86_64-linux/4.8/32: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/lib/gcc/x86_64-linux/4.8/32/crtbeginT.o: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/lib/gcc/x86_64-w64-mingw32/4.8.3/include: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/lib/gcc/x86_64-w64-mingw32/4.8.3/include/pmmintrin.h: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/ndk/r13/sources/cxx-stl/gnu-libstdc++/4.9/include/profile/impl: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/ndk/r13/sources/cxx-stl/gnu-libstdc++/4.9/include/profile/impl/profiler_hashtable_size.h: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/clang/host/linux-x86/clang-3960126/prebuilt_include/llvm/include/llvm/CodeGen: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/clang/host/linux-x86/clang-3960126/prebuilt_include/llvm/include/llvm/CodeGen/UnreachableBlockElim.h: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/lib/gcc/arm-linux-androideabi/4.9.x/include: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/lib/gcc/arm-linux-androideabi/4.9.x/include/varargs.h: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/eclipse/mavenplugins/tycho/tycho-dependencies-m2repo/org/eclipse/tycho/org.eclipse.tycho.p2.tools.shared/0.20.0: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/eclipse/mavenplugins/tycho/tycho-dependencies-m2repo/org/eclipse/tycho/org.eclipse.tycho.p2.tools.shared/0.20.0/org.eclipse.tycho.p2.tools.shared-0.20.0.jar: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/deqp/spirv/vulkan/prebuilt: lstat >>>>>>> /Volumes/android/prebuilts/deqp/spirv/vulkan/prebuilt/0x0000393e.spv: >>>>>>> too >>>>>>> many open files in system >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/include/c++/4.8/debug: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/x86_64-linux/include/c++/4.8/debug/deque: >>>>>>> >>>>>>> too many open files in system >>>>>>> /Volumes/android/prebuilts/eclipse/mavenplugins/tycho/tycho-dependencies-m2repo/org/eclipse/tycho/sisu-equinox-api/0.20.0: >>>>>>> >>>>>>> lstat >>>>>>> /Volumes/android/prebuilts/eclipse/mavenplugins/tycho/tycho-dependencies-m2repo/org/eclipse/tycho/sisu-equinox-api/0.20.0/sisu-equinox-api-0.20.0.pom: >>>>>>> >>>>>>> too many open files in system]... >>>>>>> >>>>>>> >>>>>>> #### failed to build some targets (03:25 (mm:ss)) #### >>>>>>> >>>>>> -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
