[
https://issues.apache.org/jira/browse/HADOOP-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533433
]
Joydeep Sen Sarma commented on HADOOP-2009:
-------------------------------------------
as i reported - i have already tried this out (retried just in case). On my
platform - i only see libc.so.6 as the required library.
I am wondering if it is because i don't have .so versions of lz libraries -
only .a:
[EMAIL PROTECTED] if]$ ls -l /usr/local/lib/*lzo2*
-rw-r--r-- 1 root root 847206 Feb 28 2007 /usr/local/lib/liblzo2.a
-rwxr-xr-x 1 root root 752 Feb 28 2007 /usr/local/lib/liblzo2.la
> configure script for compiling hadoop native doesn't set lzo lib name
> correctly
> -------------------------------------------------------------------------------
>
> Key: HADOOP-2009
> URL: https://issues.apache.org/jira/browse/HADOOP-2009
> Project: Hadoop
> Issue Type: Bug
> Components: build
> Affects Versions: 0.13.1
> Environment: Fedora, amd64
> Reporter: Joydeep Sen Sarma
> Assignee: Arun C Murthy
>
> Looks like this was already reported (but not resolved on the the list):
> http://tinyurl.com/2rwu6x
> I would like to compile libhadoop on amd64/Fedora and everything seems kosher
> until I hit this compile error:
> [exec]
> /home/jssarma/fbprojects/hadoop-0.13.1/src/native/src/org/apache/hadoop/io/compress/lzo/LzoCompressor.c:116:
> error: syntax error before ',' token
> the line in question is:
> // Load liblzo2.so
>
> liblzo2 = dlopen(HADOOP_LZO_LIBRARY, RTLD_LAZY | RTLD_GLOBAL);
> seems like this is being set by:
> configure:#define HADOOP_LZO_LIBRARY ${ac_cv_libname_lzo2}
> I tried executing the relevant part of configure by hand:
> if test -z "`${CC} -o conftest conftest.c -llzo2 2>&1`"; then
> if test ! -z "`which objdump`"; then
> ac_cv_libname_lzo2="`objdump -p conftest | grep NEEDED | grep lzo2 |
> sed 's/\W*NEEDED\W*\(.*\)\W*$/\
> \"\1\"/'`"
> This is not working on my system, since:
> > objdump -p conftest | grep NEEDED
> NEEDED libc.so.6
> So that would explain the compile error. Editing the configure script
> manually for now works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
