Hi Praveen,

On Wed, Mar 20, 2019 at 1:26 PM Praveen Kumar <prav...@dremio.com> wrote:

> Hi Folks,
>
> Post the CMake Refactor, we are running into issues in the Gandiva crossbow
> jobs.
>
> We are using conda to setup the dependencies currently. The following are
> the issues that we ran into
>
> 1. I am not sure if the conda forge packages are compatible in trusty (I
> was getting issues linking to boost. Sample build :
> https://travis-ci.org/praveenbingo/arrow-build/builds/508347443)
>
> 2. I am was able to work around that using a specific label
> "conda-forge/label/cf201901" which did not throw the same errors.
>
> 3. But then GTest was not linking correctly, so built GTest from source.
>
> 4. Even after that there are some linking issues :
>
> "/home/praveenkumar/CPP_TOOLCHAIN/bin/../lib/gcc/x86_64-conda_cos6-linux-gnu/7.3.0/../../../../x86_64-conda_cos6-linux-gnu/bin/ld:
> ../../release/libarrow.so.13.0.0: undefined reference to
> `icu_58::Locale::Locale(icu_58::Locale const&)'
>
> /home/praveenkumar/CPP_TOOLCHAIN/bin/../lib/gcc/x86_64-conda_cos6-linux-gnu/7.3.0/../../../../x86_64-conda_cos6-linux-gnu/bin/ld:
> ././../x86_64release-/conda_cos6libarrow.so.13.0.0-: undefined reference to
> `u_isblank_58'
>
> /home/praveenkumar/CPP_TOOLCHAIN/bin/../lib/gcc/x86_64-conda_cos6-linux-gnu/7.3.0/../../../../x86_64-conda_cos6-linux-gnu/bin/ld:
> ../../release/libarrow.so.13.0.0: undefined reference to `u_digit_58'"
>
> Any pointers on how to setup the environment in trusty?
>
> Krisitan - does any of the crossbow jobs build Gandiva on CentOs6 (or)
> Trusty?

Based on:
https://github.com/apache/arrow/tree/master/dev/tasks/linux-packages/debian.ubuntu-trusty
and
https://github.com/apache/arrow/blob/master/dev/tasks/linux-packages/yum/arrow.spec.in
I'm afraid no.

BTW We still need to fix the crossbow builds after the CMake refactor, and
ship gandiva
with the conda packages and osx/windows wheels which I'll work on the rest
of the week.

> We could then re-use the same for the Gandiva packaging work we do.
>

> Thanks a ton.
>
> Thx.
>

Reply via email to