Re: Error building cuDF on new Arrow with std::variant backport

2019-07-23 Thread Keith Kraus
Just following up in case anyone was following that this turned out to be an NVCC bug that we've reported to the relevant team internally. We moved the `ipc.cu` file to `ipc.cpp` and it works as expected with gcc. Thanks everyone! -Keith On 7/22/19, 12:52 PM, "Keith Kraus" wrote: We're w

Re: Error building cuDF on new Arrow with std::variant backport

2019-07-22 Thread Keith Kraus
We're working on that now, will report back once we have something more concrete to act on. Thanks! -Keith On 7/22/19, 12:51 PM, "Antoine Pitrou" wrote: Hi Keith, Can you try to further reduce the reduce your reproducer until you find the offending construct? Re

Re: Error building cuDF on new Arrow with std::variant backport

2019-07-22 Thread Antoine Pitrou
Hi Keith, Can you try to further reduce the reduce your reproducer until you find the offending construct? Regards Antoine. Le 22/07/2019 à 18:46, Keith Kraus a écrit : > I temporarily removed the csr related code that has the namespace clash and > confirmed that the same compilation warnin

Re: Error building cuDF on new Arrow with std::variant backport

2019-07-22 Thread Keith Kraus
I temporarily removed the csr related code that has the namespace clash and confirmed that the same compilation warnings and errors still occur. On 7/20/19, 1:03 AM, "Micah Kornfield" wrote: The namespace collision is a definite possibility, especially if you are using g++ which seems

Re: Error building cuDF on new Arrow with std::variant backport

2019-07-19 Thread Micah Kornfield
The namespace collision is a definite possibility, especially if you are using g++ which seems to be less smart about inferring types vs methods than clang is. On Fri, Jul 19, 2019 at 9:28 PM Paul Taylor wrote: > Hi Micah, > > We were able to build Arrow standalone with both c++ 11 and 14, but c

Re: Error building cuDF on new Arrow with std::variant backport

2019-07-19 Thread Paul Taylor
Hi Micah, We were able to build Arrow standalone with both c++ 11 and 14, but cuDF needs c++ 14. I found this line[1] in one of our cuda files after sending and realized we may have a collision/polluted namespace. Does that sound like a possibility? Thanks, Paul 1. https://github.com/rap

Re: Error building cuDF on new Arrow with std::variant backport

2019-07-19 Thread Micah Kornfield
Hi Paul, This actually looks like it might be a problem with arrow-4800. Did the build of arrow use c++14 or c++11? Thanks, Micah On Friday, July 19, 2019, Paul Taylor wrote: > We're updating cuDF to Arrow 0.14 but encountering errors building that > look related to PR #4259

Error building cuDF on new Arrow with std::variant backport

2019-07-19 Thread Paul Taylor
We're updating cuDF to Arrow 0.14 but encountering errors building that look related to PR #4259 . We can build Arrow itself, but we can't build cuDF when we include Arrow headers. Using C++ 14 and have tried gcc/g++ 5, 7, and clang. Has anyone seen t