Hi Dan,
Thanks for the quick response.
As you suggested, I will disable TSAN support in build-definitions,sh and
update you about it .
Meanwhile, please let me know if its advisable to wait on the kudu port
till Adar lands the reorganisation to the thirdparty ?
Regards,
Valencia
From: Dan Burkert <d...@cloudera.com>
To: kudu-dev <dev@kudu.apache.org>
Cc: Manish Patil/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS, Valencia
Serrao/Austin/Contr/IBM@IBMUS
Date: 09/23/2016 10:40 PM
Subject: Re: Kudu Build: Unsupported options error
Valencia,
If these are just issues with building libstdc++ in thirdparty, then the
effect on Kudu should be negligible. libstdc++ is *only* used (linked-to)
when building with thread sanitizer (TSAN) support. Right now we
unconditionally build thirdparty libraries for TSAN when compiling on Linux
(including libstdc++), but you could easily opt-out by changing the
conditionals here:
https://github.com/apache/kudu/blob/master/thirdparty/build-thirdparty.sh#L86
. It should also be noted that in the next few days Adar will be landing a
big reorganization to the thirdparty build that will make thirdparty
libraries build for TSAN when requested. It's also going to switch out
libstdc++ for libc++ in thirdparty (still only used for TSAN).
- Dan
On Fri, Sep 23, 2016 at 2:47 AM, Valencia Serrao <vser...@us.ibm.com>
wrote:
Hi All,
I am building Kudu 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,
