[jira] [Resolved] (CASSANDRA-11049) Conflicting definitions of VERSION string when compiling cassandra_constants

["Carl Yeksigian (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-11049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Yeksigian resolved CASSANDRA-11049.
----------------------------------------
    Resolution: Won't Fix

I'm not sure what is the root cause of this, but it is probably a new addition from the Thrift project.

As a workaround, you can rename the {{VERSION}} constant in the cassandra.thrift file before you run it through the Thrift compiler to avoid this conflict.

> Conflicting definitions of VERSION string when compiling cassandra_constants
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11049
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11049
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Peter Butler
>
> When compiling c++ code, as generated via thrift (latest version of thrift from git repository as of January 19 2016), there are conflicting versions of the VERSION constant in cassandra_constant.*   The specific error is:
> cassandra_constants.h:18:15: error: expected unqualified-id before string constant
> cassandra_constants.cpp: In constructor ‘org::apache::cassandra::cassandraConstants::cassandraConstants()’:
> cassandra_constants.cpp:14:17: error: assignment of read-only location ‘"1.0.0-dev"’
> cassandra_constants.cpp:14:17: error: incompatible types in assignment of ‘const char [8]’ to ‘const char [10]’
> The location of the original definition is in the thrift include files in config.h:
> /* Version number of package */
> #define VERSION "1.0.0-dev"
> and the 2nd definition is in cassandra_constants.cpp
> cassandraConstants::cassandraConstants() {
>   VERSION = "19.36.0";
> Note that while the thrift version is up-to-date, the cassandra version we are using is older.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)