[
https://issues.apache.org/jira/browse/HBASE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230664#comment-13230664
]
Francisco Cruz commented on HBASE-3873:
---------------------------------------
Hi all, I am having the following problem when building the hadoop snappy:
[exec] config.status: executing libtool commands
[exec] depbase=`echo
src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.lo | sed
's|[^/]*$|.deps/&|;s|\.lo$||'`;\
[exec] /bin/bash
./lsrc/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c: In function
'Java_org_apache_hadoop_io_compress_snappy_SnappyCompreibtool --tag=CC
--mode=compile gcc -DHAVE_CONFIG_H -I. -I/usr/lib/jvm/java-7-oracle/include
-I/usr/lib/jvm/java-7-oracle/inclssor_initIDs':
[exec] src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c:64:49:
error: expected expression before ',' token
[exec] src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c: In
function
'Java_org_apache_hadoop_io_compress_snappy_SnappyCompressor_compressBytesDirect':
[exec] src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c:117:3:
warning: passing argument 4 of 'dlsym_snappy_compress' from incompatible
pointer type [enabled by default]
[exec] src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c:117:3:
note: expected 'size_t *' but argument is of type 'jint *'
[exec] make: ***
[src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.lo] Error 1
[exec] ude/linux -I/home/gsd/hadoop-snappy-read-only/src/main/native/src
-Isrc/org/apache/hadoop/io/compress/snappy -I/usr/local//include -g -Wall -fPIC
-O2 -m64 -g -O2 -MT
src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.lo -MD -MP -MF
$depbase.Tpo -c -o src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.lo
src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c &&\
[exec] mv -f $depbase.Tpo $depbase.Plo
[exec] libtool: compile: gcc -DHAVE_CONFIG_H -I.
-I/usr/lib/jvm/java-7-oracle/include -I/usr/lib/jvm/java-7-oracle/include/linux
-I/home/gsd/hadoop-snappy-read-only/src/main/native/src
-Isrc/org/apache/hadoop/io/compress/snappy -I/usr/local//include -g -Wall -fPIC
-O2 -m64 -g -O2 -MT
src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.lo -MD -MP -MF
src/org/apache/hadoop/io/compress/snappy/.deps/SnappyCompressor.Tpo -c
src/org/apache/hadoop/io/compress/snappy/SnappyCompressor.c -fPIC -DPIC -o
src/org/apache/hadoop/io/compress/snappy/.libs/SnappyCompressor.o
Does anyone have any idea why is this happening?
Thanks for your help
> Mavenize Hadoop Snappy JAR/SOs project dependencies
> ---------------------------------------------------
>
> Key: HBASE-3873
> URL: https://issues.apache.org/jira/browse/HBASE-3873
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.90.2
> Environment: Linux
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Labels: build
> Fix For: 0.92.0
>
> Attachments: HBASE-3873.patch, HBASE-3873.patch
>
>
> (This JIRA builds on HBASE-3691)
> I'm working on simplifying how to use Hadoop Snappy from other based maven
> projects. The idea is that hadoop-snappy JAR and the SOs (snappy and
> hadoop-snappy) would be picked up from a Maven repository (like any other
> dependencies). SO files will be picked up based on the architecture where the
> build is running (32 or 64 bits).
> For Hbase this would remove the need to manually copy snappy JAR and SOs
> (snappy and hadoop-snappy) into HADOOP_HOME/lib or HBASE_HOME/lib and
> hadoop-snappy would be handled as a regular maven dependency (with a trick
> for the SOs file).
> The changes would affect only the pom.xml and the would be in a 'snappy'
> profile, thus requiring '-Dsnappy' option in Maven invocations to trigger the
> including of snappy JAR and SOs.
> Because hadoop-snappy (JAR and SOs) are not currently avail in public Maven
> repos, until that happens, Hbase developer would have to checkout and 'mvn
> install' hadoop-snappy. Which is (IMO) simpler than what will have to be done
> in once HBASE-3691 is committed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
