Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2693CD890 for ; Tue, 5 Mar 2013 13:21:23 +0000 (UTC) Received: (qmail 82803 invoked by uid 500); 5 Mar 2013 13:21:22 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 82108 invoked by uid 500); 5 Mar 2013 13:21:16 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 81699 invoked by uid 99); 5 Mar 2013 13:21:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Mar 2013 13:21:14 +0000 Date: Tue, 5 Mar 2013 13:21:14 +0000 (UTC) From: "Ling Kun (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8005) DemoClient.cpp can not be built correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Ling Kun created HBASE-8005: ------------------------------- Summary: 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 & 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