error of "libLLVM_host" depends on undefined module "libLLVM_darwin" reported

1,419 views
Skip to first unread message

Yongqin Liu

unread,
Mar 11, 2019, 11:35:47 PM3/11/19
to Android Building
Hi, All

With the latest AOSP master source, if I repo init with '-darwin' group excluded on my Ubuntu host,

then I will got my following errors reported:

FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
error: prebuilts/clang/host/linux-x86/Android.bp:585:1: "libLLVM_host" depends on undefined module "libLLVM_darwin"
error: prebuilts/clang/host/linux-x86/Android.bp:619:1: "libc++abi_host" depends on undefined module "libc++abi_darwin"
error: prebuilts/clang/host/linux-x86/Android.bp:595:1: "libclang_cxx_host" depends on undefined module "libclang_cxx_darwin"
error: prebuilts/clang/host/linux-x86/Android.bp:605:1: "libc++_host" depends on undefined module "libc++_darwin"
ninja: build stopped: subcommand failed.
23:14:17 soong bootstrap failed with: exit status 1


I found that libLLVM_darwin module is defined in project of prebuilts/clang/host/darwin-x86/,
but does those modules defined in prebuilts/clang/host/linux-x86 really depends on the modules defined in prebuilts/clang/host/darwin-x86?
and it worked before(one week ago?) without  prebuilts/clang/host/darwin-x86 repo synced.
Could  anyone please help to check on that?

Thanks,
Yongqin Liu

Dan Willemsen

unread,
Mar 12, 2019, 1:53:39 AM3/12/19
to Android Building
We don't maintain the -darwin group -- in general, if you have a manifest that hasn't been carefully stripped down, you may need to specify ALLOW_MISSING_DEPENDENCIES=true, but that may only push the error until later in the build process (and won't work in this case).

In this case, it looks like the change in behavior was due to this soong change: https://android-review.googlesource.com/c/platform/build/soong/+/920955 (the parent change is the implementation). We're now adding dependencies to all the referenced modules, even if they're in target: { darwin: { ... } } blocks that will never be used in the current build. While that can be a good thing (you're less likely to cause an instant build failure on Mac due to a typo), it is a problem for these types of use cases.

I've filed a public bug to track this: https://issuetracker.google.com/128377112

Thanks for the report,
Dan

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
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 android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yongqin Liu

unread,
Mar 13, 2019, 2:30:54 AM3/13/19
to android-...@googlegroups.com
On Tue, 12 Mar 2019 at 13:53, 'Dan Willemsen' via Android Building <android-...@googlegroups.com> wrote:
We don't maintain the -darwin group -- in general, if you have a manifest that hasn't been carefully stripped down, you may need to specify ALLOW_MISSING_DEPENDENCIES=true, but that may only push the error until later in the build process (and won't work in this case).

In this case, it looks like the change in behavior was due to this soong change: https://android-review.googlesource.com/c/platform/build/soong/+/920955 (the parent change is the implementation). We're now adding dependencies to all the referenced modules, even if they're in target: { darwin: { ... } } blocks that will never be used in the current build. While that can be a good thing (you're less likely to cause an instant build failure on Mac due to a typo), it is a problem for these types of use cases.

I've filed a public bug to track this: https://issuetracker.google.com/128377112
Thanks for checking on this, will following there.

Best Regards,
Yongqin Liu
You received this message because you are subscribed to a topic in the Google Groups "Android Building" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-building/FeG_-xYZPTQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-buildi...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
Best Regards,
Yongqin Liu
---------------------------------------------------------------
#mailing list
linaro-...@lists.linaro.org
Reply all
Reply to author
Forward
0 new messages