I should add that the last option about "disabling" kudu we've found to be painful in practice and may cause you to have some issues running/testing. If it's possible to move forward with the toolchain compilation I would strongly recommend that.
On Thu, Sep 22, 2016 at 9:13 AM, Matthew Jacobs <[email protected]> wrote: > Any modifications you make to the Kudu build would probably need to be > checked by the folks working on the Kudu project. Impala builds Kudu > for 2 reasons: 1) for the client which it links against (build time > dependency) 2) for the dev environment (dev and test dependency). > > What are you trying to do? If you want Impala to work on ppc64le, then > you'll probably eventually want Kudu to work on ppc64le as well, and > that might take a lot more work/testing. > > If you want the impala that you build to be able to communicate with > Kudu at all (whether or not Kudu runs on the same platform), you do > need to compile in the client as you're currently doing. In that case, > you should ask the Kudu authors at [email protected]. > > If you're OK with not supporting any Kudu for now, then you can > "disable" Kudu support in the build/runtime. To do this, you should: > 1) in native-toolchain: > get source/kudu/build.sh is_supported_platform() to return false > for ppc64le > that results in a stub being built instead of all of kudu > 2) in Impala: changing impala-config.sh so IS_KUDU_SUPPORTED is false > for ppc64le. > > On Wed, Sep 21, 2016 at 10:45 PM, Valencia Serrao <[email protected]> wrote: >> >> Hi All, >> >> I am building Impala-toolchain on ppc64le. However, while building Kudu's >> thirdparty "libstdc++-v3", I have encountered following errors: >> Error1: clang-3.8: error: unsupported option '-print-multi-os-directory' >> Error2: clang-3.8: error: unknown argument: '-mlong-double-64' >> >> I couldn't find any documentation to find the equivalent options to be used >> on ppc64le. To get around the Error1, , I have removed the >> -print-multi-os-directory option and continued with the build. >> >> The build has surely progressed with this work-around, however, I need to >> know: >> 1. What is the impact of removing "-print-multi-os-directory" ? Will it >> significantly affect the functionality for Impala ? >> 2. Can I take the same approach for the Error2 ? What will be the impact on >> functionality ? >> 3. If removing the above two options has a significant impact, then, could >> you share the documentation/equivalent options to be used for ppc64le ? >> >> Any pointers on this issue will be helpful. >> >> Regards, >> Valencia
