kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: Building from Source fails on my CentOS 7.2
Date Tue, 18 Apr 2017 03:17:47 GMT
Hmm. I think kudu should work fine against your old version, but you may
need to explicitly make sure it picks up the right path for all the related
libraries at link time (libkrb5, k5crypto, and krb5support). If it mixed
versions across these you will probably see errors.

Todd

On Apr 17, 2017 8:01 PM, "Jason Heo" <jason.heo.sde@gmail.com> wrote:

> Hi Todd.
>
> Good point!
>
> It turned out that the customized krb5 library was pre-installed by my
> infrastructure team. and it is a old version.
>
> $ ldd /usr/lib64/libkrb5.so | grep k5cry
> libk5crypto.so.3 => /usr/path/to/lib/libk5crypto.so.3 (0x00007f4f17b23000)
>
> Thanks,
>
> Jason.
>
> 2017-04-18 4:00 GMT+09:00 Todd Lipcon <todd@cloudera.com>:
>
>> Hi Jason,
>>
>> This is interesting. It seems like for some reason your libkrb5.so isn't
>> properly linekd against libkrb5support.so. On a fresh CentOS 7.3 system I
>> just booted, after installing krb5-devel packages, I see the symbols
>> defined in the expected libraries:
>>
>> [root@todd-el7 ~]# ldd /usr/lib64/libkrb5.so | grep k5cry
>>         libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f8c68d34000)
>> [root@todd-el7 ~]# objdump -T /lib64/libk5crypto.so.3 | grep
>> enctype_to_name
>> 0000000000019cd0 g    DF .text  000000000000012b  k5crypto_3_MIT
>> krb5_enctype_to_name
>>
>> Do you have the MIT krb5 dev libraries installed, or is it possible you
>> have heimdal or some other krb5 implementation?
>>
>> -Todd
>>
>> On Thu, Apr 13, 2017 at 10:00 PM, Jason Heo <jason.heo.sde@gmail.com>
>> wrote:
>>
>>> Hello.
>>>
>>> I'm using CentOS 7.2
>>>
>>> To build from Source Code, I followed the manual
>>> <https://kudu.apache.org/docs/installation.html#build_from_source> (except
>>> for Re Hat Developer Toolset because I use CentOS 7.2)
>>>
>>> Though I failed to compile :(
>>>
>>> ```
>>> ...
>>> [ 31%] Building CXX object src/kudu/master/CMakeFiles/mas
>>> ter.dir/sys_catalog.cc.o
>>> [ 31%] Building CXX object src/kudu/master/CMakeFiles/mas
>>> ter.dir/ts_descriptor.cc.o
>>> [ 31%] Building CXX object src/kudu/master/CMakeFiles/mas
>>> ter.dir/ts_manager.cc.o
>>> [ 31%] Linking CXX static library ../../../lib/libmaster.a
>>> [ 31%] Built target master
>>> [ 31%] Built target krb5_realm_override
>>> Scanning dependencies of target kudu-master
>>> [ 32%] Building CXX object src/kudu/master/CMakeFiles/kud
>>> u-master.dir/master_main.cc.o
>>> [ 32%] Linking CXX executable ../../../bin/kudu-master
>>> /usr/lib64/libkrb5.so: undefined reference to
>>> `krb5_enctype_to_name@k5crypto_3_MIT'
>>> /usr/lib64/libkrb5.so: undefined reference to
>>> `k5_buf_free@krb5support_0_MIT'
>>> /usr/lib64/libkrb5.so: undefined reference to
>>> `krb5int_utf8_to_ucs4@krb5support_0_MIT'
>>> ...
>>> ```
>>>
>>> BTW, I'm building from source code so that I use `kudu fs check`. Can I
>>> use "fs check" command if I checkout master branch?
>>>
>>> Versions
>>> -------
>>>
>>> $ rpm -qf /usr/lib64/libkrb5.so
>>> krb5-devel-1.14.1-27.el7_3.x86_64 <= Newest version for CentOS 7.2 yum
>>> repos.
>>>
>>> $ g++ --version
>>> g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11)
>>> Copyright (C) 2015 Free Software Foundation, Inc.
>>> This is free software; see the source for copying conditions.  There is
>>> NO
>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>>> PURPOSE.
>>>
>>>
>>> Thanks,
>>>
>>> Jason.
>>>
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>
>
>

Mime
View raw message