strlcpy seams to be correctly defined in liblustreapi of all 2.x
versions we checked. But not this 2.5.39-ddn6.
I suggest you report this linking issue to you DDN support.
Regards
Le 18/12/2015 02:36, Nathan Dauchy - NOAA Affiliate wrote:
Greetings Everyone,
We are trying to get to the latest-and-greatest (stable) versions and
running into compilation problems. Any ideas of where to look for a
solution would be appreciated! Using the following combination,
Robinhood does not build with lustre or changelog support:
CentOS-6.7
kernel-2.6.32-573.12.1.el6.x86_64
lustre-2.5.39-ddn6
robinhood-2.5.5-2
The error was first identified with:
[root@sherwood ~]# robinhood --version
Product: robinhood
Version: 2.5.5-2
Build: 2015-12-17 22:07:33
Compilation switches:
Temporary filesystem manager
Address entries by path
MDT Changelogs disabled
No Lustre support
Database binding: MySQL
Here is how Lustre and Robinhood were built:
# yum localinstall
lustre-source-2.5.39-ddn6_2.6.32_504.30.3.el6_lustre.ddn1.x86_64_g4b5fd9f.x86_64.rpm
# cd /usr/src/lustre-2.5.39
# ./configure --with-linux=/usr/src/kernels/`uname -r`
--disable-server --enable-quota --enable-mpitests=no
# make -j 24 rpms
# cd /root/rpmbuild/RPMS/x86_64/
# rpm -Uvh lustre-client{,-modules,-debuginfo}-2.*.rpm
# shutdown -r now
# cd ~/robinhood-2.5.5
# ./configure --with-purpose=TMPFS --with-lustre=/usr/src/lustre-2.5.39
# make rpm
# rpm -Uvh rpms/RPMS/x86_64/robinhood-*.rpm
The lustre support seems to be disabled after this test failing in the
Robinhood configure step, from the "config.log" file:
configure:16008: checking for llapi_obd_statfs in -llustreapi
configure:16044: gcc -o conftest -g -O2
-I/usr/src/lustre-2.5.39/lustre/include
-L/usr/src/lustre-2.5.39/lustre/utils conftest.c -llustreapi >&5
/usr/src/lustre-2.5.39/lustre/utils/liblustreapi.so: undefined
reference to `strlcpy'
collect2: ld returned 1 exit status
configure:16051: $? = 1
...
CHANGELOGS_FALSE=''
CHANGELOGS_TRUE='#'
...
LUSTRE=''
LUSTRE_FALSE=''
LUSTRE_HSM_FALSE=''
LUSTRE_HSM_TRUE='#'
LUSTRE_TRUE='#'
I also tried a slightly older Lustre version (2.5.37-ddn7), but that
had the same problem. Rolling back the kernel is possible, but to be
avoided if at all possible so we can get the latest security fixes.
My hope is that there is a simple change to how we are building
robinhood or lustre, or a patch to one or the other, which will allow
us to move forward.
Thanks much for any suggestions!
-Nathan
------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
http://www.avast.com
------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
