I will keep the error and the build script in sync to reflect the latest
error. Currently, it says
```
arrow/compute/kernels/scalar_string_internal.h:216:20: error: unused
function 'StringClassifyDoc' [-Werror,-Wunused-function]
```

My end goal is to conda package a debug build.

On Thu, Mar 17, 2022 at 3:11 PM Chak-Pong Chung <chakpongch...@gmail.com>
wrote:

> Hi Weston,
>
> Thank you for taking a look at this. I have updated the build-arrow.sh
> script and checked the yml for dependencies as you suggested.
>
>
> https://drive.google.com/file/d/1F3vlIXsf_9-RAhmuIiEPLAi_CXpECgUq/view?usp=sharing
>
>
> https://drive.google.com/file/d/10hjHQ7UQ6uLAVAlvZA4MvQ24cIQ0GNrM/view?usp=sharing
>
> You should be able to reproduce the error as the log shown in this log
> folder here:
>
>
> https://drive.google.com/drive/folders/1RuhCwgc-UFOUth3ooXbpSvoFBLEk7E7v?usp=sharing
>
>
>
> Now the error is about the file not found.
> e.g.
> `fatal error: 'cstdint' file not found
> #include <cstdint>`
>
> I am using clang-13 with -std=c++11 as shown in the log. Could you please
> advise?
>
>
> On Tue, Mar 15, 2022 at 11:03 PM Weston Pace <weston.p...@gmail.com>
> wrote:
>
>> If you can include the full failed build log that may help.  I did
>> confirm that I can build ninja-debug-gandiva though I had to install
>> considerably more conda dependencies than the ones you listed (e.g.
>> boost, gmock, gflags, etc).  Presumably you have these in your base
>> conda environment or installed at the system level.
>>
>> > /usr/bin/ld: cannot find /lib64/libpthread.so.0
>> > /usr/bin/ld: cannot find /usr/lib64/libpthread_nonshared.a
>>
>> My best guess for this error is something related to [1] which states
>> that installing setuptools into a conda environment the wrong way
>> could lead to setuptools' installation corrupting the conda
>> environment.  I did not see this error in any of my testing.
>>
>> > Does it work with clang build? If so, which version of clang? If not,
>> which
>> > version of GCC should I use?
>>
>> Yes, Arrow can be compiled with either clang or gcc.  The CI tests
>> several versions of each.
>>
>> > CMake Error at
>> >
>> /home/jimmy/miniconda3/envs/pokeai/lib/cmake/BoostDetectToolset-1.77.0.cmake:5
>> > (string):
>> >   string sub-command REGEX, mode MATCHALL needs at least 5 arguments
>> > total to
>> >   command.
>>
>> I was able to reproduce Jimmy's error by following the included steps.
>> The problem is this statement:
>>
>>     export CXX=~/miniconda3/envs/pokeai/bin/clang-cpp
>>
>> This should instead be:
>>
>>     export CXX=~/miniconda3/envs/pokeai/bin/clang++
>>
>> [1]
>> https://stackoverflow.com/questions/71340058/conda-does-not-look-for-libpthread-and-libpthread-nonshared-at-the-right-place-w
>>
>> On Mon, Feb 21, 2022 at 5:38 PM jimmy <jimmyqmc...@gmail.com> wrote:
>> >
>> > I tried to build using "ninja-debug-maximal" - Debug build with
>> > everything enabled (except benchmarks and CUDA)
>> >
>> >
>> >
>> > I have same problem, I tried to build the release 7.0.0 branch using
>> > conda environment with dependencies yml mentioned in the link below
>> >
>> > <
>> https://drive.google.com/file/d/1F3vlIXsf_9-RAhmuIiEPLAi_CXpECgUq/view?usp=sharing
>> >
>> >
>> > with following steps:
>> >
>> > <
>> https://drive.google.com/file/d/10hjHQ7UQ6uLAVAlvZA4MvQ24cIQ0GNrM/view?usp=sharing
>> >
>> >
>> > It does not work with following errors
>> >
>> > CMake Error at
>> >
>> /home/jimmy/miniconda3/envs/pokeai/lib/cmake/BoostDetectToolset-1.77.0.cmake:5
>> > (string):
>> >   string sub-command REGEX, mode MATCHALL needs at least 5 arguments
>> > total to
>> >   command.
>> > Call Stack (most recent call first):
>> >
>> >
>> /home/jimmy/miniconda3/envs/pokeai/lib/cmake/boost_system-1.77.0/boost_system-config.cmake:29
>> > (include)
>> >
>> >
>> /home/jimmy/miniconda3/envs/pokeai/lib/cmake/Boost-1.77.0/BoostConfig.cmake:141
>> > (find_package)
>> >
>> >
>> /home/jimmy/miniconda3/envs/pokeai/lib/cmake/Boost-1.77.0/BoostConfig.cmake:258
>> > (boost_find_component)
>> >   /snap/cmake/1005/share/cmake-3.22/Modules/FindBoost.cmake:594
>> > (find_package)
>> >   cmake_modules/FindBoostAlt.cmake:41 (find_package)
>> >   cmake_modules/ThirdpartyToolchain.cmake:241 (find_package)
>> >   cmake_modules/ThirdpartyToolchain.cmake:956 (resolve_dependency)
>> >   CMakeLists.txt:546 (include)
>> >
>> >
>> > Can anyone share the build instruction steps?
>> >
>> >
>> > On 2022/02/21 01:37:49 Chak-Pong Chung wrote:
>> >  > I just tried `--preset ninja-debug-basic`, same error.
>> >  >
>> >  > When trying with `--preset ninja-debug-maximal`,
>> >  >
>> >  > <https://anaconda.org/search?q=librados>
>> >  >
>> >  > Does it work with clang build? If so, which version of clang? If
>> > not, which
>> >  > version of GCC should I use?
>> >  >
>> >  > I tried the 6.0.1 and 7.0.0 release.
>> >  >
>> >  > On Sun, Feb 20, 2022 at 12:24 PM Chak-Pong Chung <ch...@gmail.com>
>> >  > wrote:
>> >  >
>> >  > > I am trying to create a debug build for arrow  and gandiva to be
>> > used in
>> >  > > c++, possibly in python as well.
>> >  > >
>> >  > > Using the following step
>> >  > >
>> >  > > cd $ARROW_SOURCE_DIR
>> >  > > cd cpp
>> >  > >
>> >  > > rm -rf build
>> >  > > mkdir build
>> >  > > cd build/
>> >  > >
>> >  > > cmake .. \
>> >  > > -DBUILD_WARNING_LEVEL=PRODUCTION \
>> >  > > --preset ninja-debug-gandiva
>> >  > > cmake --build . -j 14
>> >  > >
>> >  > > shows an error:
>> >  > > ```
>> >  > > /usr/bin/ld: cannot find /lib64/libpthread.so.0
>> >  > > /usr/bin/ld: cannot find /usr/lib64/libpthread_nonshared.a
>> >  > > clang: error: linker command failed with exit code 1 (use -v to see
>> >  > > invocation)
>> >  > > ```
>> >  > >
>> >  > > I am doing it inside a conda environment with :
>> >  > >
>> >  > > ```
>> >  > >
>> >  > > # mamba install -c conda-forge gmock
>> >  > > # mamba install -c conda-forge gtest
>> >  > > # mamba install -c conda-forge google-cloud-cpp
>> >  > >
>> >  > > ```
>> >  > > Any idea?
>> >  > > --
>> >  > > Regards,
>> >  > > Chak-Pong
>> >  > >
>> >  >
>> >  >
>> >  > --
>> >  > Regards,
>> >  > Chak-Pong
>> >  >
>> >
>> >
>> >
>>
>
>
> --
> Regards,
> Chak-Pong
>


-- 
Regards,
Chak-Pong

Reply via email to