You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ling Kun (JIRA)" <ji...@apache.org> on 2013/03/05 14:25:12 UTC

[jira] [Commented] (HBASE-8005) DemoClient.cpp can not be built correctly

    [ https://issues.apache.org/jira/browse/HBASE-8005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593393#comment-13593393 ] 

Ling Kun commented on HBASE-8005:
---------------------------------

The patch:

diff --git a/hbase-examples/src/main/cpp/Makefile b/hbase-examples/src/main/cpp/Makefile
index aab5951..30ffef4 100644
--- a/hbase-examples/src/main/cpp/Makefile
+++ b/hbase-examples/src/main/cpp/Makefile
@@ -28,7 +28,7 @@ GEN_SRC = ./gen-cpp/Hbase.cpp \
 default: DemoClient
 
 DemoClient: DemoClient.cpp
-       g++ -o DemoClient -I${THRIFT_DIR}  -I./gen-cpp -L${LIB_DIR} -Wl,-rpath,${LIB_DIR} -lthrift DemoClient.cpp ${GEN_SRC}
+       g++ -o DemoClient -I${THRIFT_DIR}  -I./gen-cpp -L${LIB_DIR} -Wl,-rpath,${LIB_DIR} DemoClient.cpp ${GEN_SRC} -lthrift
 
 clean:
        rm -rf DemoClient

                
> DemoClient.cpp   can not be built correctly
> -------------------------------------------
>
>                 Key: HBASE-8005
>                 URL: https://issues.apache.org/jira/browse/HBASE-8005
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>    Affects Versions: 0.94.5
>            Reporter: Ling Kun
>
> when compile the DemoClient.cpp within the latest HBase release package, it seems that this file is out of date(plenty of APIs need a new std::map<Text, Text> & attributes parameter ). And I have also tried to replace  the DemoClient.cpp with the latest trunk version. However, after some modification there are still link problems when compile the code( undefined reference to  `apache::thrift::transport::TSocket::TSocket(std::string, int)', I have passed the -lthrift parameter to gcc).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira