from:"Xiaoshuang LU $JIRA$"


[ 
https://issues.apache.org/jira/browse/THRIFT-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824855#comment-15824855
 ] 

Xiaoshuang LU commented on THRIFT-4032:
---

Hi [~jensg], appears that 0.10.0 has been released in 2017-01-03, right?

{code}
References
1. http://thrift.apache.org/
2. https://github.com/apache/thrift/releases
{code}

> no libthrift 0.10.0 in 
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> --
>
> Key: THRIFT-4032
> URL: https://issues.apache.org/jira/browse/THRIFT-4032
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.10.0
>Reporter: Xiaoshuang LU
>
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> {code}
> Index of /maven2/org/apache/thrift/libthrift/
> ../
> 0.6.1/ 2011-04-25 08:54   
>  -
> 0.7.0/ 2011-08-13 17:27   
>  -
> 0.8.0/ 2011-11-29 18:34   
>  -
> 0.9.0/ 2012-10-15 21:50   
>  -
> 0.9.1/ 2013-08-23 10:26   
>  -
> 0.9.2/ 2014-11-18 12:19   
>  -
> 0.9.3/ 2015-10-11 21:19   
>  -
> maven-metadata.xml 2015-10-11 21:19   
>519
> maven-metadata.xml.md5 2015-10-11 21:19   
> 32
> maven-metadata.xml.sha12015-10-11 21:19   
> 40
> {code}



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

[jira] [Updated] (THRIFT-4032) no libthrift 0.10.0 in https://repo1.maven.org/maven2/org/apache/thrift/libthrift/


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

Xiaoshuang LU updated THRIFT-4032:
--
Component/s: (was: Deployment)
 Build Process

> no libthrift 0.10.0 in 
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> --
>
> Key: THRIFT-4032
> URL: https://issues.apache.org/jira/browse/THRIFT-4032
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.10.0
>Reporter: Xiaoshuang LU
>Priority: Blocker
>
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> {code}
> Index of /maven2/org/apache/thrift/libthrift/
> ../
> 0.6.1/ 2011-04-25 08:54   
>  -
> 0.7.0/ 2011-08-13 17:27   
>  -
> 0.8.0/ 2011-11-29 18:34   
>  -
> 0.9.0/ 2012-10-15 21:50   
>  -
> 0.9.1/ 2013-08-23 10:26   
>  -
> 0.9.2/ 2014-11-18 12:19   
>  -
> 0.9.3/ 2015-10-11 21:19   
>  -
> maven-metadata.xml 2015-10-11 21:19   
>519
> maven-metadata.xml.md5 2015-10-11 21:19   
> 32
> maven-metadata.xml.sha12015-10-11 21:19   
> 40
> {code}



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

[jira] [Updated] (THRIFT-4032) no libthrift 0.10.0 in https://repo1.maven.org/maven2/org/apache/thrift/libthrift/


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

Xiaoshuang LU updated THRIFT-4032:
--
Affects Version/s: 0.10.0

> no libthrift 0.10.0 in 
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> --
>
> Key: THRIFT-4032
> URL: https://issues.apache.org/jira/browse/THRIFT-4032
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.10.0
>Reporter: Xiaoshuang LU
>Priority: Blocker
>
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> {code}
> Index of /maven2/org/apache/thrift/libthrift/
> ../
> 0.6.1/ 2011-04-25 08:54   
>  -
> 0.7.0/ 2011-08-13 17:27   
>  -
> 0.8.0/ 2011-11-29 18:34   
>  -
> 0.9.0/ 2012-10-15 21:50   
>  -
> 0.9.1/ 2013-08-23 10:26   
>  -
> 0.9.2/ 2014-11-18 12:19   
>  -
> 0.9.3/ 2015-10-11 21:19   
>  -
> maven-metadata.xml 2015-10-11 21:19   
>519
> maven-metadata.xml.md5 2015-10-11 21:19   
> 32
> maven-metadata.xml.sha12015-10-11 21:19   
> 40
> {code}



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

[jira] [Created] (THRIFT-4032) no libthrift 0.10.0 in https://repo1.maven.org/maven2/org/apache/thrift/libthrift/

Xiaoshuang LU created THRIFT-4032:
-

 Summary: no libthrift 0.10.0 in 
https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
 Key: THRIFT-4032
 URL: https://issues.apache.org/jira/browse/THRIFT-4032
 Project: Thrift
  Issue Type: Bug
  Components: Deployment
Reporter: Xiaoshuang LU
Priority: Blocker


{code}
Index of /maven2/org/apache/thrift/libthrift/

../
0.6.1/ 2011-04-25 08:54 
   -
0.7.0/ 2011-08-13 17:27 
   -
0.8.0/ 2011-11-29 18:34 
   -
0.9.0/ 2012-10-15 21:50 
   -
0.9.1/ 2013-08-23 10:26 
   -
0.9.2/ 2014-11-18 12:19 
   -
0.9.3/ 2015-10-11 21:19 
   -
maven-metadata.xml 2015-10-11 21:19 
 519
maven-metadata.xml.md5 2015-10-11 21:19 
  32
maven-metadata.xml.sha12015-10-11 21:19 
  40
{code}



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

[jira] [Updated] (THRIFT-4032) no libthrift 0.10.0 in https://repo1.maven.org/maven2/org/apache/thrift/libthrift/


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

Xiaoshuang LU updated THRIFT-4032:
--
Description: 
https://repo1.maven.org/maven2/org/apache/thrift/libthrift/

{code}
Index of /maven2/org/apache/thrift/libthrift/

../
0.6.1/ 2011-04-25 08:54 
   -
0.7.0/ 2011-08-13 17:27 
   -
0.8.0/ 2011-11-29 18:34 
   -
0.9.0/ 2012-10-15 21:50 
   -
0.9.1/ 2013-08-23 10:26 
   -
0.9.2/ 2014-11-18 12:19 
   -
0.9.3/ 2015-10-11 21:19 
   -
maven-metadata.xml 2015-10-11 21:19 
 519
maven-metadata.xml.md5 2015-10-11 21:19 
  32
maven-metadata.xml.sha12015-10-11 21:19 
  40
{code}

  was:
{code}
Index of /maven2/org/apache/thrift/libthrift/

../
0.6.1/ 2011-04-25 08:54 
   -
0.7.0/ 2011-08-13 17:27 
   -
0.8.0/ 2011-11-29 18:34 
   -
0.9.0/ 2012-10-15 21:50 
   -
0.9.1/ 2013-08-23 10:26 
   -
0.9.2/ 2014-11-18 12:19 
   -
0.9.3/ 2015-10-11 21:19 
   -
maven-metadata.xml 2015-10-11 21:19 
 519
maven-metadata.xml.md5 2015-10-11 21:19 
  32
maven-metadata.xml.sha12015-10-11 21:19 
  40
{code}


> no libthrift 0.10.0 in 
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> --
>
> Key: THRIFT-4032
> URL: https://issues.apache.org/jira/browse/THRIFT-4032
> Project: Thrift
>  Issue Type: Bug
>  Components: Deployment
>Reporter: Xiaoshuang LU
>Priority: Blocker
>
> https://repo1.maven.org/maven2/org/apache/thrift/libthrift/
> {code}
> Index of /maven2/org/apache/thrift/libthrift/
> ../
> 0.6.1/ 2011-04-25 08:54   
>  -
> 0.7.0/ 2011-08-13 17:27   
>  -
> 0.8.0/ 2011-11-29 18:34   
>  -
> 0.9.0/ 2012-10-15 21:50   
>  -
> 0.9.1/ 2013-08-23 10:26   
>  -
> 0.9.2/ 2014-11-18 12:19   
>  -
> 0.9.3/ 2015-10-11 21:19   
>  -
> maven-metadata.xml 2015-10-11 21:19   
>519
> maven-metadata.xml.md5 2015-10-11 21:19   
> 32
> maven-metadata.xml.sha12015-10-11 21:19   
> 40
> {code}



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

[jira] [Commented] (THRIFT-3207) Enable build with OpenSSL 1.1.x

2016-12-01 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713667#comment-15713667
 ] 

Xiaoshuang LU commented on THRIFT-3207:
---

Yes. This issue is duplicated by THRIFT-3736 and latest code of master branch 
can be built with OpenSSL 1.1.0c.

> Enable build with OpenSSL 1.1.x
> ---
>
> Key: THRIFT-3207
> URL: https://issues.apache.org/jira/browse/THRIFT-3207
> Project: Thrift
>  Issue Type: Improvement
>  Components: C++ - Library
>Affects Versions: 0.9.2
>Reporter: Paweł Janicki
>Priority: Minor
>  Labels: easyfix
> Attachments: THRIFT-3207.patch
>
>
> As thrift requires OpenSSL v1.1.0 there are still some problems with 
> compiling latest official releases on Visual Studio 2013. We falled back to 
> other OpenSSL releases that source version can be compiled without problems.
> Unfortunately Thrift can not be build against OpenSSL pre 1.1.0 due to 
> missing TLSv1_1_method() and TLSv1_2_method().
> While OpenSSL in version 0.9.8 and 1.0.0 is supported till 
> [2015-12-31|https://www.openssl.org/about/releasestrat.html] and Open SSL in 
> version 1.0.1 and 1.0.2 is supported till 
> [2016-12-31|https://www.openssl.org/about/releasestrat.html] we found 
> reasonable to enable this releases to be used for Thrift builds.
> The proposed patch enables Thrift support of TLS 1.1 and 1.2 only when build 
> with OpenSSL 1.1.0 or newer.



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

[jira] [Updated] (THRIFT-3991) compiler plugin relies on boost


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

Xiaoshuang LU updated THRIFT-3991:
--
Description: 
{code}
[root@localhost thrift]# make 
make  all-recursive
make[1]: Entering directory `/data/thrift'
Making all in lib/cpp
make[2]: Entering directory `/data/thrift/lib/cpp'
Making all in .
make[3]: Entering directory `/data/thrift/lib/cpp'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/data/thrift/lib/cpp'
make[2]: Leaving directory `/data/thrift/lib/cpp'
Making all in compiler/cpp
make[2]: Entering directory `/data/thrift/compiler/cpp'
Making all in src
make[3]: Entering directory `/data/thrift/compiler/cpp/src'
make  all-am
make[4]: Entering directory `/data/thrift/compiler/cpp/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/data/thrift/compiler/cpp/src'
make[3]: Leaving directory `/data/thrift/compiler/cpp/src'
Making all in src/thrift/plugin
make[3]: Entering directory `/data/thrift/compiler/cpp/src/thrift/plugin'
make  all-am
make[4]: Entering directory `/data/thrift/compiler/cpp/src/thrift/plugin'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/data/thrift/compiler/cpp/src/thrift/plugin'
make[3]: Leaving directory `/data/thrift/compiler/cpp/src/thrift/plugin'
Making all in .
make[3]: Entering directory `/data/thrift/compiler/cpp'
/bin/sh ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../.. -I../../lib/cpp/src/thrift -I../../lib/c_glib/src/thrift  -I./src -Isrc 
-I../../lib/cpp/src -DTHRIFT_ENABLE_PLUGIN=1  -Wall -Wextra -pedantic -g -O2 
-MT src/thrift/plugin/libthriftc_la-plugin.lo -MD -MP -MF 
src/thrift/plugin/.deps/libthriftc_la-plugin.Tpo -c -o 
src/thrift/plugin/libthriftc_la-plugin.lo `test -f 
'src/thrift/plugin/plugin.cc' || echo './'`src/thrift/plugin/plugin.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I../../lib/cpp/src/thrift 
-I../../lib/c_glib/src/thrift -I./src -Isrc -I../../lib/cpp/src 
-DTHRIFT_ENABLE_PLUGIN=1 -Wall -Wextra -pedantic -g -O2 -MT 
src/thrift/plugin/libthriftc_la-plugin.lo -MD -MP -MF 
src/thrift/plugin/.deps/libthriftc_la-plugin.Tpo -c src/thrift/plugin/plugin.cc 
-o src/thrift/plugin/libthriftc_la-plugin.o
In file included from ./src/thrift/plugin/plugin.h:23:0,
 from src/thrift/plugin/plugin.cc:20:
../../lib/cpp/src/thrift/Thrift.h:45:39: fatal error: 
boost/utility/enable_if.hpp: No such file or directory
 #include 
   ^
compilation terminated.
make[3]: *** [src/thrift/plugin/libthriftc_la-plugin.lo] Error 1
make[3]: Leaving directory `/data/thrift/compiler/cpp'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/data/thrift/compiler/cpp'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/data/thrift'
make: *** [all] Error 2
{code}

> compiler plugin relies on boost
> ---
>
> Key: THRIFT-3991
> URL: https://issues.apache.org/jira/browse/THRIFT-3991
> Project: Thrift
>  Issue Type: Bug
>  Components: Compiler (General)
>Affects Versions: 0.10.0
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3991.patch
>
>
> {code}
> [root@localhost thrift]# make 
> make  all-recursive
> make[1]: Entering directory `/data/thrift'
> Making all in lib/cpp
> make[2]: Entering directory `/data/thrift/lib/cpp'
> Making all in .
> make[3]: Entering directory `/data/thrift/lib/cpp'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory `/data/thrift/lib/cpp'
> make[2]: Leaving directory `/data/thrift/lib/cpp'
> Making all in compiler/cpp
> make[2]: Entering directory `/data/thrift/compiler/cpp'
> Making all in src
> make[3]: Entering directory `/data/thrift/compiler/cpp/src'
> make  all-am
> make[4]: Entering directory `/data/thrift/compiler/cpp/src'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory `/data/thrift/compiler/cpp/src'
> make[3]: Leaving directory `/data/thrift/compiler/cpp/src'
> Making all in src/thrift/plugin
> make[3]: Entering directory `/data/thrift/compiler/cpp/src/thrift/plugin'
> make  all-am
> make[4]: Entering directory `/data/thrift/compiler/cpp/src/thrift/plugin'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory `/data/thrift/compiler/cpp/src/thrift/plugin'
> make[3]: Leaving directory `/data/thrift/compiler/cpp/src/thrift/plugin'
> Making all in .
> make[3]: Entering directory `/data/thrift/compiler/cpp'
> /bin/sh ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../.. -I../../lib/cpp/src/thrift -I../../lib/c_glib/src/thrift  -I./src 
> -Isrc -I../../lib/cpp/src -DTHRIFT_ENABLE_PLUGIN=1  -Wall -Wextra -pedantic 
> -g -O2 -MT src/thrift/plugin/libthriftc_la-plugin.lo -MD -MP -MF 
> src/thrift/plugin/.deps/libthriftc_la-plugin.Tpo -c -o 
>

[jira] [Updated] (THRIFT-3991) compiler plugin relies on boost


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

Xiaoshuang LU updated THRIFT-3991:
--
Attachment: THRIFT-3991.patch

> compiler plugin relies on boost
> ---
>
> Key: THRIFT-3991
> URL: https://issues.apache.org/jira/browse/THRIFT-3991
> Project: Thrift
>  Issue Type: Bug
>  Components: Compiler (General)
>Affects Versions: 0.10.0
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3991.patch
>
>




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

[jira] [Created] (THRIFT-3991) compiler plugin relies on boost

Xiaoshuang LU created THRIFT-3991:
-

 Summary: compiler plugin relies on boost
 Key: THRIFT-3991
 URL: https://issues.apache.org/jira/browse/THRIFT-3991
 Project: Thrift
  Issue Type: Bug
  Components: Compiler (General)
Affects Versions: 0.10.0
Reporter: Xiaoshuang LU






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

[jira] [Comment Edited] (THRIFT-3207) Enable build with OpenSSL pre 1.1.0


[ 
https://issues.apache.org/jira/browse/THRIFT-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15710740#comment-15710740
 ] 

Xiaoshuang LU edited comment on THRIFT-3207 at 12/1/16 3:34 AM:


Hi [~jensg], would you please modify ticket name to "Enable build with OpenSSL 
1.1.0 series" and close this issue? Thank you.


was (Author: in-chief):
Hi [~jensg], would please close this issue? Thank you.

> Enable build with OpenSSL pre 1.1.0
> ---
>
> Key: THRIFT-3207
> URL: https://issues.apache.org/jira/browse/THRIFT-3207
> Project: Thrift
>  Issue Type: Improvement
>  Components: C++ - Library
>Affects Versions: 0.9.2
>Reporter: Paweł Janicki
>Priority: Minor
>  Labels: easyfix
> Attachments: THRIFT-3207.patch
>
>
> As thrift requires OpenSSL v1.1.0 there are still some problems with 
> compiling latest official releases on Visual Studio 2013. We falled back to 
> other OpenSSL releases that source version can be compiled without problems.
> Unfortunately Thrift can not be build against OpenSSL pre 1.1.0 due to 
> missing TLSv1_1_method() and TLSv1_2_method().
> While OpenSSL in version 0.9.8 and 1.0.0 is supported till 
> [2015-12-31|https://www.openssl.org/about/releasestrat.html] and Open SSL in 
> version 1.0.1 and 1.0.2 is supported till 
> [2016-12-31|https://www.openssl.org/about/releasestrat.html] we found 
> reasonable to enable this releases to be used for Thrift builds.
> The proposed patch enables Thrift support of TLS 1.1 and 1.2 only when build 
> with OpenSSL 1.1.0 or newer.



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

[jira] [Commented] (THRIFT-3207) Enable build with OpenSSL pre 1.1.0


[ 
https://issues.apache.org/jira/browse/THRIFT-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15710740#comment-15710740
 ] 

Xiaoshuang LU commented on THRIFT-3207:
---

Hi [~jensg], would please close this issue? Thank you.

> Enable build with OpenSSL pre 1.1.0
> ---
>
> Key: THRIFT-3207
> URL: https://issues.apache.org/jira/browse/THRIFT-3207
> Project: Thrift
>  Issue Type: Improvement
>  Components: C++ - Library
>Affects Versions: 0.9.2
>Reporter: Paweł Janicki
>Priority: Minor
>  Labels: easyfix
> Attachments: THRIFT-3207.patch
>
>
> As thrift requires OpenSSL v1.1.0 there are still some problems with 
> compiling latest official releases on Visual Studio 2013. We falled back to 
> other OpenSSL releases that source version can be compiled without problems.
> Unfortunately Thrift can not be build against OpenSSL pre 1.1.0 due to 
> missing TLSv1_1_method() and TLSv1_2_method().
> While OpenSSL in version 0.9.8 and 1.0.0 is supported till 
> [2015-12-31|https://www.openssl.org/about/releasestrat.html] and Open SSL in 
> version 1.0.1 and 1.0.2 is supported till 
> [2016-12-31|https://www.openssl.org/about/releasestrat.html] we found 
> reasonable to enable this releases to be used for Thrift builds.
> The proposed patch enables Thrift support of TLS 1.1 and 1.2 only when build 
> with OpenSSL 1.1.0 or newer.



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

[jira] [Comment Edited] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682784#comment-15682784
 ] 

Xiaoshuang LU edited comment on THRIFT-3979 at 11/21/16 7:39 AM:
-

Hi [~jking], I proposed TExtendedBinaryProtocol before I heard THeader. Jens 
told me that THeader can be used for customers' options about 3 days ago.

It seems that my old description is a litter bit confusing and makes you think 
what I want is security functionalities. So I just explain my solution more 
precisely.

Thanks.


was (Author: in-chief):
Hi [~jking], Jens has already told me that THeader can be used for customers' 
options. But I proposed TExtendedBinaryProtocol before I knew THeader.

It seems that my old description is a litter bit confusing and makes you think 
what I want is security functionalities. So I just explain my solution more 
precisely.

Thanks.

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (whatever customers want) in each 
> request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Commented] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682784#comment-15682784
 ] 

Xiaoshuang LU commented on THRIFT-3979:
---

Hi [~jking], Jens has already told me that THeader can be used for customers' 
options. And I proposed TExtendedBinaryProtocol before I knew THeader.

It seems that my old description is a litter bit confusing and makes you think 
what I want is security functionalities. So I just explain my solution more 
precisely.

Thanks.

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (whatever customers want) in each 
> request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Comment Edited] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682784#comment-15682784
 ] 

Xiaoshuang LU edited comment on THRIFT-3979 at 11/21/16 7:33 AM:
-

Hi [~jking], Jens has already told me that THeader can be used for customers' 
options. But I proposed TExtendedBinaryProtocol before I knew THeader.

It seems that my old description is a litter bit confusing and makes you think 
what I want is security functionalities. So I just explain my solution more 
precisely.

Thanks.


was (Author: in-chief):
Hi [~jking], Jens has already told me that THeader can be used for customers' 
options. And I proposed TExtendedBinaryProtocol before I knew THeader.

It seems that my old description is a litter bit confusing and makes you think 
what I want is security functionalities. So I just explain my solution more 
precisely.

Thanks.

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (whatever customers want) in each 
> request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Comment Edited] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682294#comment-15682294
 ] 

Xiaoshuang LU edited comment on THRIFT-3979 at 11/21/16 2:42 AM:
-

[~jking], thanks for your detailed comments.

In fact, TExtendedBinaryProtocol is meant to give customers ability to have 
whatever they want in requests and responses. I just use username and password 
as examples. I will revise the issue description.

Again, thank you.


was (Author: in-chief):
[~jking] thanks for your detailed comments.

In fact, TExtendedBinaryProtocol is meant to give customers ability to have 
whatever they want in requests and responses. I just use username and password 
as examples. I will revise the issue description.

Again, thank you.

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (whatever customers want) in each 
> request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Commented] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682300#comment-15682300
 ] 

Xiaoshuang LU commented on THRIFT-3979:
---

Understood. Thank you, [~nsuke].

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (whatever customers want) in each 
> request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Updated] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


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

Xiaoshuang LU updated THRIFT-3979:
--
Description: 
Sometimes, customers wanna put some options (whatever customers want) in each 
request and response. And these options ought to be transparent for 
applications.

Unfortunately, thrift protocol does not have good extensibility for extra 
functionalities. I would like to propose the following solution to address this 
issue.

1. TMessage adds a new field called "options"
2. customers set "options"
3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked

  was:
Sometimes, customers wanna put some options (username, password, id, etc.) in 
each request and response. And these options ought to be transparent for 
applications.

Unfortunately, thrift protocol does not have good extensibility for extra 
functionalities. I would like to propose the following solution to address this 
issue.

1. TMessage adds a new field called "options"
2. customers set "options"
3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked


> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (whatever customers want) in each 
> request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Commented] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682294#comment-15682294
 ] 

Xiaoshuang LU commented on THRIFT-3979:
---

[~jking] thanks for your detailed comments.

In fact, TExtendedBinaryProtocol is meant to give customers ability to have 
whatever they want in requests and responses. I just use username and password 
as examples. I will revise the issue description.

Again, thank you.

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: Wish List
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (username, password, id, etc.) in 
> each request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Commented] (THRIFT-3979) offer TExtendedBinaryProtocol for customers

2016-11-18 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676702#comment-15676702
 ] 

Xiaoshuang LU commented on THRIFT-3979:
---

Hi [~jensg], thanks for your information. I appreciate it.

I have some questions about the Header things.

1. Shall we keep the compability between this Header and old protocols. e.g. 
what is the expected behavior if one side uses Header while the other uses old 
protocol (assuming TBinaryProtocol)?

2. Appears that TFramedTransport is redundant since the leading 4 bytes or 12 
bytes of Header describe the size of following Protocol Data Unit.

> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: C++ - Library, Java - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (username, password, id, etc.) in 
> each request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Updated] (THRIFT-3979) offer TExtendedBinaryProtocol for customers


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

Xiaoshuang LU updated THRIFT-3979:
--
Description: 
Sometimes, customers wanna put some options (username, password, id, etc.) in 
each request and response. And these options ought to be transparent for 
applications.

Unfortunately, thrift protocol does not have good extensibility for extra 
functionalities. I would like to propose the following solution to address this 
issue.

1. TMessage adds a new field called "options"
2. customers set "options"
3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked

  was:
Sometimes, customers wanna put some options (username, password, id, etc.) in 
each request and response. And these options ought to be transparent for 
applications. Unfortunately, thrift protocol does not have good extensibility 
for extra functionalities.

I would like to propose the following solution to address this issue.

1. TMessage adds a new field called "options"
2. customers set "options"
3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked


> offer TExtendedBinaryProtocol for customers
> ---
>
> Key: THRIFT-3979
> URL: https://issues.apache.org/jira/browse/THRIFT-3979
> Project: Thrift
>  Issue Type: Story
>  Components: C++ - Library, Java - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Sometimes, customers wanna put some options (username, password, id, etc.) in 
> each request and response. And these options ought to be transparent for 
> applications.
> Unfortunately, thrift protocol does not have good extensibility for extra 
> functionalities. I would like to propose the following solution to address 
> this issue.
> 1. TMessage adds a new field called "options"
> 2. customers set "options"
> 3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
> 4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Updated] (THRIFT-3980) add TExtendedBinaryProtocol.java


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

Xiaoshuang LU updated THRIFT-3980:
--
Attachment: THRIFT-3980.patch

> add TExtendedBinaryProtocol.java
> 
>
> Key: THRIFT-3980
> URL: https://issues.apache.org/jira/browse/THRIFT-3980
> Project: Thrift
>  Issue Type: Sub-task
>  Components: Java - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3980.patch
>
>




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

[jira] [Created] (THRIFT-3980) add TExtendedBinaryProtocol.java

Xiaoshuang LU created THRIFT-3980:
-

 Summary: add TExtendedBinaryProtocol.java
 Key: THRIFT-3980
 URL: https://issues.apache.org/jira/browse/THRIFT-3980
 Project: Thrift
  Issue Type: Sub-task
  Components: Java - Library
Affects Versions: 0.9.3
Reporter: Xiaoshuang LU






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

[jira] [Created] (THRIFT-3979) offer TExtendedBinaryProtocol for customers

Xiaoshuang LU created THRIFT-3979:
-

 Summary: offer TExtendedBinaryProtocol for customers
 Key: THRIFT-3979
 URL: https://issues.apache.org/jira/browse/THRIFT-3979
 Project: Thrift
  Issue Type: Story
  Components: C++ - Library, Java - Library
Affects Versions: 0.9.3
Reporter: Xiaoshuang LU


Sometimes, customers wanna put some options (username, password, id, etc.) in 
each request and response. And these options ought to be transparent for 
applications. Unfortunately, thrift protocol does not have good extensibility 
for extra functionalities.

I would like to propose the following solution to address this issue.

1. TMessage adds a new field called "options"
2. customers set "options"
3. TExtendedBinaryProtocol writes "options" when "writeMessageBegin" invoked
4. TExtendedBinaryProtocol reads "options" when "readMessageBegin" invoked



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

[jira] [Comment Edited] (THRIFT-3871) configure failed on CentOS 6


[ 
https://issues.apache.org/jira/browse/THRIFT-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367092#comment-15367092
 ] 

Xiaoshuang LU edited comment on THRIFT-3871 at 7/8/16 1:58 AM:
---

Hi [~jking], this problem is caused by customer installed automake. i.e. 
configure of thrift 0.9.3 works well and there is nothing to fix. Thanks, James.


was (Author: in-chief):
Hi [~jking], this problem is caused by customer installed automake. It also 
means that configure of thrift 0.9.3 works well and there is nothing to fix. 
Thanks, James.

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /data/binutils-2.26/bin/ld
> checking if the linker (/data/binutils-2.26bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... 
> /data/binutils-2.26/bin/nm -B
> checking the name lister (/data/binutils-2.26/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /data/binutils-2.26/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /data/binutils-2.26/bin/nm -B output from gcc 
> object... ok
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking whether we are using the GNU C++ compiler... (cached) yes
> checking whether g++ accepts -g... (cached) yes
> checking dependency style of g++... (cached) gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC

[jira] [Commented] (THRIFT-3871) configure failed on CentOS 6


[ 
https://issues.apache.org/jira/browse/THRIFT-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367092#comment-15367092
 ] 

Xiaoshuang LU commented on THRIFT-3871:
---

Hi [~jking], this problem is caused by customer installed automake. It also 
means that configure of thrift 0.9.3 works well and there is nothing to fix. 
Thanks, James.

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /data/binutils-2.26/bin/ld
> checking if the linker (/data/binutils-2.26bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... 
> /data/binutils-2.26/bin/nm -B
> checking the name lister (/data/binutils-2.26/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /data/binutils-2.26/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /data/binutils-2.26/bin/nm -B output from gcc 
> object... ok
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking whether we are using the GNU C++ compiler... (cached) yes
> checking whether g++ accepts -g... (cached) yes
> checking dependency style of g++... (cached) gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the

[jira] [Resolved] (THRIFT-3871) configure failed on CentOS 6


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

Xiaoshuang LU resolved THRIFT-3871.
---
Resolution: Not A Problem

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /data/binutils-2.26/bin/ld
> checking if the linker (/data/binutils-2.26bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... 
> /data/binutils-2.26/bin/nm -B
> checking the name lister (/data/binutils-2.26/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /data/binutils-2.26/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /data/binutils-2.26/bin/nm -B output from gcc 
> object... ok
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking whether we are using the GNU C++ compiler... (cached) yes
> checking whether g++ accepts -g... (cached) yes
> checking dependency style of g++... (cached) gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/data/binutils-2.26/bin/ld -m elf_x86_64) 
> supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode

[jira] [Comment Edited] (THRIFT-3871) configure failed on CentOS 6


[ 
https://issues.apache.org/jira/browse/THRIFT-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365702#comment-15365702
 ] 

Xiaoshuang LU edited comment on THRIFT-3871 at 7/7/16 6:55 AM:
---

ROOT CAUSES

automake 1.15 is installed to CentOS 6 from scratch despite the distribution 
has already offer a default one (automake 1.11.1) along with some extended 
aclocal macros. Unfortunately, these macros are not included in the search path 
of automake 1.15. As a result, configure cannot handle PKG_CHECK_MODULES 
correctly and refuse to continue.

This issue can be addressed by the following steps.

{code}
$ ACLOCAL_PATH=/usr/share/aclocal sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}


was (Author: in-chief):
Root Causes:

automake 1.15 is installed to CentOS 6 from scratch despite the distribution 
has already offer a default one (automake 1.11.1) along with some extended 
aclocal macros. Unfortunately, these macros are not included in the search path 
of automake 1.15. As a result, configure cannot handle PKG_CHECK_MODULES 
correctly and refuse to continue.

This issue can be addressed by the following steps.

{code}
$ ACLOCAL_PATH=/usr/share/aclocal sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type...

[jira] [Comment Edited] (THRIFT-3871) configure failed on CentOS 6


[ 
https://issues.apache.org/jira/browse/THRIFT-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365702#comment-15365702
 ] 

Xiaoshuang LU edited comment on THRIFT-3871 at 7/7/16 6:54 AM:
---

Root Causes:

automake 1.15 is installed to CentOS 6 from scratch despite the distribution 
has already offer a default one (automake 1.11.1) along with some extended 
aclocal macros. Unfortunately, these macros are not included in the search path 
of automake 1.15. As a result, configure cannot handle PKG_CHECK_MODULES 
correctly and refuse to continue.

This issue can be addressed by the following steps.

{code}
$ ACLOCAL_PATH=/usr/share/aclocal sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}


was (Author: in-chief):
Root Causes:

automake 1.15 is installed to CentOS 6 from scratch despite there is already a 
default one (automake 1.11.1).  Unfortunately, pkg.m4 file is not included in 
the search path of new automake. As a result, configure cannot handle 
PKG_CHECK_MODULES correctly and refuse to continue.

We can do the following steps to address this issue.

{code}
$ ACLOCAL_PATH=/usr/share/aclocal sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
${code}

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not

[jira] [Commented] (THRIFT-3871) configure failed on CentOS 6


[ 
https://issues.apache.org/jira/browse/THRIFT-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365702#comment-15365702
 ] 

Xiaoshuang LU commented on THRIFT-3871:
---

Root Causes:

automake 1.15 is installed to CentOS 6 from scratch despite there is already a 
default one (automake 1.11.1).  Unfortunately, pkg.m4 file is not included in 
the search path of new automake. As a result, configure cannot handle 
PKG_CHECK_MODULES correctly and refuse to continue.

We can do the following steps to address this issue.

{code}
$ ACLOCAL_PATH=/usr/share/aclocal sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
${code}

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> ./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /data/binutils-2.26/bin/ld
> checking if the linker (/data/binutils-2.26bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... 
> /data/binutils-2.26/bin/nm -B
> checking the name lister (/data/binutils-2.26/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /data/binutils-2.26/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /data/binutils-2.26/bin/nm -B output from gcc 
> object... ok
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h...

[jira] [Updated] (THRIFT-3871) configure failed on CentOS 6

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

Xiaoshuang LU updated THRIFT-3871:
--
Description:
Reproduce Steps
{code}
# https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0
--with-libevent=/data/libevent-2.0.22-stable
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5
--without-c_glib --without-csharp --without-java --without-erlang
--without-nodejs --without-lua --without-python --without-perl --without-php
--without-php_extension --without-ruby --without-haskell --without-go
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

Errors
{code}
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
./configure: line 3894: PKG_PROG_PKG_CONFIG: command not found
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /data/binutils-2.26/bin/ld
checking if the linker (/data/binutils-2.26bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)...
/data/binutils-2.26/bin/nm -B
checking the name lister (/data/binutils-2.26/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 3458764513820540925
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /data/binutils-2.26/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /data/binutils-2.26/bin/nm -B output from gcc
object... ok
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/data/binutils-2.26/bin/ld -m elf_x86_64)
supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for ld used by g++... /data/binutils-2.26/bin/ld -m elf_x86_64
checking if the linker (/data/binutils-2.26/bin/ld -m elf_x86_64) is GNU ld...
yes
checking whether the g++ linker (/data/binutils-2.26/bin/ld -m elf_x86_64)
supports shared libraries... yes
checking for g++

[jira] [Updated] (THRIFT-3871) configure failed on CentOS 6


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

Xiaoshuang LU updated THRIFT-3871:
--
Summary: configure failed on CentOS 6  (was: configure failed on CentOS)

> configure failed on CentOS 6
> 
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>
> Reproduce Steps
> {code}
> # https://github.com/apache/thrift/archive/0.9.3.tar.gz
> $ sh bootstrap.sh
> $ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
> --with-libevent=/data/libevent-2.0.22-stable 
> --with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
> --enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
> --without-c_glib --without-csharp --without-java --without-erlang 
> --without-nodejs --without-lua --without-python --without-perl --without-php 
> --without-php_extension --without-ruby --without-haskell --without-go 
> --without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
> -fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
> {code}
> Errors
> {code}
> ./configure: line 17096: syntax error near unexpected token `QT,'
> ./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork 
> >= 4.3, have_qt=yes, have_qt=no)'
> {code}
> Workarounds
> {code}
> diff --git a/configure.ac b/configure.ac
> index 18e3233..bd03b30 100755
> --- a/configure.ac
> +++ b/configure.ac
> @@ -155,7 +155,8 @@ if test "$with_cpp" = "yes";  then
>AX_THRIFT_LIB(qt4, [Qt], yes)
>have_qt=no
>if test "$with_qt4" = "yes";  then
> -PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
> have_qt=no)
> +cd .
> +#PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
> have_qt=no)
>fi
>if test "$have_qt" = "yes"; then
>  AC_PATH_PROGS([QT_MOC], [moc-qt4 moc], "fail")
> @@ -168,9 +169,10 @@ if test "$with_cpp" = "yes";  then
>have_qt5=no
>qt_reduce_reloc=""
>if test "$with_qt5" = "yes";  then
> -PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
> -  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
> --variable=qt_config Qt5Core | grep "reduce_relocations"`],
> -  [have_qt5=no])
> +cd .
> +#PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
> +#  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
> --variable=qt_config Qt5Core | grep "reduce_relocations"`],
> +#  [have_qt5=no])
>fi
>if test "$have_qt5" = "yes"; then
>  AC_PATH_PROGS([QT5_MOC], [moc-qt5 moc], "fail")
> @@ -188,8 +190,8 @@ AM_CONDITIONAL([QT5_REDUCE_RELOCATIONS], [test 
> "x$qt_reduce_reloc" != "x"])
>  
>  AX_THRIFT_LIB(c_glib, [C (GLib)], yes)
>  if test "$with_c_glib" = "yes"; then
> -  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
> -  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
> have_gobject2=no)
> +#  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, 
> have_glib2=no)
> +#  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
> have_gobject2=no)
>if test "$have_glib2" = "yes" -a "$have_gobject2" = "yes" ; then
>  have_c_glib="yes"
>fi
> @@ -198,15 +200,15 @@ AM_CONDITIONAL(WITH_C_GLIB, [test "$have_glib2" = "yes" 
> -a "$have_gobject2" = "y
>  
>  AX_THRIFT_LIB(csharp, [C#], yes)
>  if test "$with_csharp" = "yes";  then
> -  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
> +#  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
>if test "$mono_2_11" == "yes"; then
>  AC_PATH_PROG([MCS], [mcs])
>  if test "x$MCS" != "x"; then
>mono_mcs="yes"
>  fi
>fi
> -  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
> -  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
> +#  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
> +#  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
>if test "$have_mono" = "yes" ; then
>  have_csharp="yes"
>fi
> {code}
> By the way, http://www-us.apache.org/dist/thrift/0.9.3/thrift-0.9.3.tar.gz is 
> not the same as https://github.com/apache/thrift/archive/0.9.3.tar.gz. The 
> former includes configure file while the latter requires users to run 
> bootstrap.sh first.



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

[jira] [Updated] (THRIFT-3871) configure failed on CentOS


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

Xiaoshuang LU updated THRIFT-3871:
--
Description: 
Reproduce Steps
{code}
# https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

Errors
{code}
./configure: line 17096: syntax error near unexpected token `QT,'
./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
{code}

Workarounds
{code}
diff --git a/configure.ac b/configure.ac
index 18e3233..bd03b30 100755
--- a/configure.ac
+++ b/configure.ac
@@ -155,7 +155,8 @@ if test "$with_cpp" = "yes";  then
   AX_THRIFT_LIB(qt4, [Qt], yes)
   have_qt=no
   if test "$with_qt4" = "yes";  then
-PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
have_qt=no)
+cd .
+#PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
have_qt=no)
   fi
   if test "$have_qt" = "yes"; then
 AC_PATH_PROGS([QT_MOC], [moc-qt4 moc], "fail")
@@ -168,9 +169,10 @@ if test "$with_cpp" = "yes";  then
   have_qt5=no
   qt_reduce_reloc=""
   if test "$with_qt5" = "yes";  then
-PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
-  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
--variable=qt_config Qt5Core | grep "reduce_relocations"`],
-  [have_qt5=no])
+cd .
+#PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
+#  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
--variable=qt_config Qt5Core | grep "reduce_relocations"`],
+#  [have_qt5=no])
   fi
   if test "$have_qt5" = "yes"; then
 AC_PATH_PROGS([QT5_MOC], [moc-qt5 moc], "fail")
@@ -188,8 +190,8 @@ AM_CONDITIONAL([QT5_REDUCE_RELOCATIONS], [test 
"x$qt_reduce_reloc" != "x"])
 
 AX_THRIFT_LIB(c_glib, [C (GLib)], yes)
 if test "$with_c_glib" = "yes"; then
-  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
-  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
have_gobject2=no)
+#  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
+#  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
have_gobject2=no)
   if test "$have_glib2" = "yes" -a "$have_gobject2" = "yes" ; then
 have_c_glib="yes"
   fi
@@ -198,15 +200,15 @@ AM_CONDITIONAL(WITH_C_GLIB, [test "$have_glib2" = "yes" 
-a "$have_gobject2" = "y
 
 AX_THRIFT_LIB(csharp, [C#], yes)
 if test "$with_csharp" = "yes";  then
-  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
   if test "$mono_2_11" == "yes"; then
 AC_PATH_PROG([MCS], [mcs])
 if test "x$MCS" != "x"; then
   mono_mcs="yes"
 fi
   fi
-  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
-  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
   if test "$have_mono" = "yes" ; then
 have_csharp="yes"
   fi
{code}

By the way, http://www-us.apache.org/dist/thrift/0.9.3/thrift-0.9.3.tar.gz is 
not the same as https://github.com/apache/thrift/archive/0.9.3.tar.gz. The 
former includes configure file while the latter requires users to run 
bootstrap.sh first.

  was:
Reproduce Steps
{code}
# https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

Errors
{code}
./configure: line 17096: syntax error near unexpected token `QT,'
./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
{code}

Workarounds

[jira] [Updated] (THRIFT-3871) configure failed on CentOS


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

Xiaoshuang LU updated THRIFT-3871:
--
Description: 
Reproduce Steps
{code}
# https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

Errors
{code}
./configure: line 17096: syntax error near unexpected token `QT,'
./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
{code}

Workarounds
{code}
diff --git a/configure.ac b/configure.ac
index 18e3233..bd03b30 100755
--- a/configure.ac
+++ b/configure.ac
@@ -155,7 +155,8 @@ if test "$with_cpp" = "yes";  then
   AX_THRIFT_LIB(qt4, [Qt], yes)
   have_qt=no
   if test "$with_qt4" = "yes";  then
-PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
have_qt=no)
+cd .
+#PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
have_qt=no)
   fi
   if test "$have_qt" = "yes"; then
 AC_PATH_PROGS([QT_MOC], [moc-qt4 moc], "fail")
@@ -168,9 +169,10 @@ if test "$with_cpp" = "yes";  then
   have_qt5=no
   qt_reduce_reloc=""
   if test "$with_qt5" = "yes";  then
-PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
-  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
--variable=qt_config Qt5Core | grep "reduce_relocations"`],
-  [have_qt5=no])
+cd .
+#PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
+#  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
--variable=qt_config Qt5Core | grep "reduce_relocations"`],
+#  [have_qt5=no])
   fi
   if test "$have_qt5" = "yes"; then
 AC_PATH_PROGS([QT5_MOC], [moc-qt5 moc], "fail")
@@ -188,8 +190,8 @@ AM_CONDITIONAL([QT5_REDUCE_RELOCATIONS], [test 
"x$qt_reduce_reloc" != "x"])
 
 AX_THRIFT_LIB(c_glib, [C (GLib)], yes)
 if test "$with_c_glib" = "yes"; then
-  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
-  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
have_gobject2=no)
+#  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
+#  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
have_gobject2=no)
   if test "$have_glib2" = "yes" -a "$have_gobject2" = "yes" ; then
 have_c_glib="yes"
   fi
@@ -198,15 +200,15 @@ AM_CONDITIONAL(WITH_C_GLIB, [test "$have_glib2" = "yes" 
-a "$have_gobject2" = "y
 
 AX_THRIFT_LIB(csharp, [C#], yes)
 if test "$with_csharp" = "yes";  then
-  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
   if test "$mono_2_11" == "yes"; then
 AC_PATH_PROG([MCS], [mcs])
 if test "x$MCS" != "x"; then
   mono_mcs="yes"
 fi
   fi
-  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
-  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
   if test "$have_mono" = "yes" ; then
 have_csharp="yes"
   fi
{code}

By the way
http://www-us.apache.org/dist/thrift/0.9.3/thrift-0.9.3.tar.gz is not the same 
as https://github.com/apache/thrift/archive/0.9.3.tar.gz. The former package 
includes configure file while the later requires users to run bootstrap.sh 
first.

  was:
{code}
# https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

{code}
./configure: line 17096: syntax error near unexpected token `QT,'
./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
{code}

Workarounds
{code}
diff --git

[jira] [Updated] (THRIFT-3871) configure failed on CentOS


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

Xiaoshuang LU updated THRIFT-3871:
--
Description: 
{code}
# https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"
{code}

{code}
./configure: line 17096: syntax error near unexpected token `QT,'
./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
{code}

Workarounds
{code}
diff --git a/configure.ac b/configure.ac
index 18e3233..bd03b30 100755
--- a/configure.ac
+++ b/configure.ac
@@ -155,7 +155,8 @@ if test "$with_cpp" = "yes";  then
   AX_THRIFT_LIB(qt4, [Qt], yes)
   have_qt=no
   if test "$with_qt4" = "yes";  then
-PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
have_qt=no)
+cd .
+#PKG_CHECK_MODULES([QT], [QtCore >= 4.3, QtNetwork >= 4.3], have_qt=yes, 
have_qt=no)
   fi
   if test "$have_qt" = "yes"; then
 AC_PATH_PROGS([QT_MOC], [moc-qt4 moc], "fail")
@@ -168,9 +169,10 @@ if test "$with_cpp" = "yes";  then
   have_qt5=no
   qt_reduce_reloc=""
   if test "$with_qt5" = "yes";  then
-PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
-  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
--variable=qt_config Qt5Core | grep "reduce_relocations"`],
-  [have_qt5=no])
+cd .
+#PKG_CHECK_MODULES([QT5], [Qt5Core >= 5.0, Qt5Network >= 5.0],
+#  [have_qt5=yes;qt_reduce_reloc=`$PKG_CONFIG 
--variable=qt_config Qt5Core | grep "reduce_relocations"`],
+#  [have_qt5=no])
   fi
   if test "$have_qt5" = "yes"; then
 AC_PATH_PROGS([QT5_MOC], [moc-qt5 moc], "fail")
@@ -188,8 +190,8 @@ AM_CONDITIONAL([QT5_REDUCE_RELOCATIONS], [test 
"x$qt_reduce_reloc" != "x"])
 
 AX_THRIFT_LIB(c_glib, [C (GLib)], yes)
 if test "$with_c_glib" = "yes"; then
-  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
-  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
have_gobject2=no)
+#  PKG_CHECK_MODULES([GLIB], [glib-2.0 >= 2.0], have_glib2=yes, have_glib2=no)
+#  PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.0], have_gobject2=yes, 
have_gobject2=no)
   if test "$have_glib2" = "yes" -a "$have_gobject2" = "yes" ; then
 have_c_glib="yes"
   fi
@@ -198,15 +200,15 @@ AM_CONDITIONAL(WITH_C_GLIB, [test "$have_glib2" = "yes" 
-a "$have_gobject2" = "y
 
 AX_THRIFT_LIB(csharp, [C#], yes)
 if test "$with_csharp" = "yes";  then
-  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 2.11.0, mono_2_11=yes, mono_2_11=no)
   if test "$mono_2_11" == "yes"; then
 AC_PATH_PROG([MCS], [mcs])
 if test "x$MCS" != "x"; then
   mono_mcs="yes"
 fi
   fi
-  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
-  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 2.0.0, net_3_5=yes, net_3_5=no)
+#  PKG_CHECK_MODULES(MONO, mono >= 1.2.4, have_mono=yes, have_mono=no)
   if test "$have_mono" = "yes" ; then
 have_csharp="yes"
   fi
{code}

  was:
$ wget -c https://github.com/apache/thrift/archive/0.9.3.tar.gz
$ sh bootstrap.sh
$ ./configure --prefix=/data/thrift-0.9.3 --with-boost=/data/boost-1.61.0 
--with-libevent=/data/libevent-2.0.22-stable 
--with-openssl=/data/openssl-1.0.2h --with-zlib=/data/zlib-1.2.8 
--enable-shared=no --enable-static=yes --with-cpp --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --without-go 
--without-haxe --without-d --disable-tests --disable-tutorial CFLAGS="-m64 
-fPIC -g0 -O3" CXXFLAGS="-m64 -fPIC -g0 -O3"

I have encountered
{code}
./configure: line 17096: syntax error near unexpected token `QT,'
./configure: line 17096: `PKG_CHECK_MODULES(QT, QtCore >= 4.3, QtNetwork >= 
4.3, have_qt=yes, have_qt=no)'
{code}


> configure failed on CentOS
> --
>
> Key: THRIFT-3871
> URL: https://issues.apache.org/jira/browse/THRIFT-3871
> Project: Thrift
>  Issue Type: Bug
>  Components: Build Process
>Affects Versions: 0.9.3
>

[jira] [Comment Edited] (THRIFT-3320) TMessages of multiplexed service responses of should include service names

2016-06-22 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345792#comment-15345792
 ] 

Xiaoshuang LU edited comment on THRIFT-3320 at 6/23/16 5:40 AM:


Hi [~jking3], Thanks for your comments.

At present, thrift doesn't not offer users a pure and complete asynchronous 
interface suite. Developers cannot write PDUs to a transport concurrently.

Assuming that thrift has thread-safe transports and a set of asynchronous 
Interfaces in future releases, how to deserialize *_results from transports if 
"TMultiplexedProtocol"s are leveraged?

In my proposal, we can get service names after "TMessage"s are parsed. With 
service names and procedure names, specific instances of *_results can be 
selected to read data from transport.

If we just store the IDs of requests,  a mapping between id and *_result shall 
be maintained. And this is not elegant.


was (Author: in-chief):
Hi [~jking3], Thanks for your comments.

At present, thrift doesn't not offer users a pure and complete asynchronous 
interface suite. Developers cannot write PDUs to a transport concurrently.

Assuming that thrift has thread-safe transports and a set of asynchronous 
Interfaces in future releases, how to deserialize *_args and *_results from 
transports if "TMultiplexedProtocol"s are leveraged?

In my proposal, we can get service names after "TMessage"s are parsed. With 
service names and procedure names, specific instances of *_args and *_results 
can be selected to read data from transport.



> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Story
>  Components: C++ - Library, Java - Library, Python - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>




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

[jira] [Commented] (THRIFT-3320) TMessages of multiplexed service responses of should include service names

2016-06-22 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345792#comment-15345792
 ] 

Xiaoshuang LU commented on THRIFT-3320:
---

Hi [~jking3], Thanks for your comments.

At present, thrift doesn't not offer users a pure and complete asynchronous 
interface suite. Developers cannot write PDUs to a transport concurrently.

Assuming that thrift has thread-safe transports and a set of asynchronous 
Interfaces in future releases, how to deserialize *_args and *_results from 
transports if "TMultiplexedProtocol"s are leveraged?

In my proposal, we can get service names after "TMessage"s are parsed. With 
service names and procedure names, specific instances of *_args and *_results 
can be selected to read data from transport.



> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Story
>  Components: C++ - Library, Java - Library, Python - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>




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

[jira] [Updated] (THRIFT-3518) TConcurrentClientSyncInfo files were missing for Visual Studio


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

Xiaoshuang LU updated THRIFT-3518:
--
Description: 
$. add TestService.thrift
{code}
namespace cpp test

service TestService
{
i32 test(1:i32 data1, 2:string data2);
}
{code}

$. compile TestService.thrift
{code}
thrift --strict --gen cpp --out . TestService.thrift
{code}

$. build with Visual Studio
{code}
SeverityCodeDescription Project FileLine
Error   LNK2019 unresolved external symbol "public: __cdecl 
apache::thrift::async::TConcurrentSendSentry::TConcurrentSendSentry(class 
apache::thrift::async::TConcurrentClientSyncInfo *)" 
(??0TConcurrentSendSentry@async@thrift@apache@@QEAA@PEAVTConcurrentClientSyncInfo@123@@Z)
 referenced in function "public: int __cdecl 
test::TestServiceConcurrentClient::send_test(int,class 
std::basic_string const &)" 
(?send_test@TestServiceConcurrentClient@test@@QEAAHHAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)

blah blah blah
{code}

  was:
$. thrift file
{code}
namespace cpp test

service TestService
{
i32 test(1:i32 data1, 2:string data2);
}
{code}

$. compile thrift file
{code}
thrift --strict --gen cpp --out . TestService.thrift
{code}

$. build with Visual Studio
{code}
SeverityCodeDescription Project FileLine
Error   LNK2019 unresolved external symbol "public: __cdecl 
apache::thrift::async::TConcurrentSendSentry::TConcurrentSendSentry(class 
apache::thrift::async::TConcurrentClientSyncInfo *)" 
(??0TConcurrentSendSentry@async@thrift@apache@@QEAA@PEAVTConcurrentClientSyncInfo@123@@Z)
 referenced in function "public: int __cdecl 
test::TestServiceConcurrentClient::send_test(int,class 
std::basic_string const &)" 
(?send_test@TestServiceConcurrentClient@test@@QEAAHHAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)

blah blah blah
{code}


> TConcurrentClientSyncInfo files were missing for Visual Studio
> --
>
> Key: THRIFT-3518
> URL: https://issues.apache.org/jira/browse/THRIFT-3518
> Project: Thrift
>  Issue Type: Bug
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>Priority: Blocker
> Fix For: 0.9.4
>
> Attachments: THRIFT-3518.patch
>
>
> $. add TestService.thrift
> {code}
> namespace cpp test
> service TestService
> {
> i32 test(1:i32 data1, 2:string data2);
> }
> {code}
> $. compile TestService.thrift
> {code}
> thrift --strict --gen cpp --out . TestService.thrift
> {code}
> $. build with Visual Studio
> {code}
> Severity  CodeDescription Project FileLine
> Error LNK2019 unresolved external symbol "public: __cdecl 
> apache::thrift::async::TConcurrentSendSentry::TConcurrentSendSentry(class 
> apache::thrift::async::TConcurrentClientSyncInfo *)" 
> (??0TConcurrentSendSentry@async@thrift@apache@@QEAA@PEAVTConcurrentClientSyncInfo@123@@Z)
>  referenced in function "public: int __cdecl 
> test::TestServiceConcurrentClient::send_test(int,class 
> std::basic_string std::allocator > const &)" 
> (?send_test@TestServiceConcurrentClient@test@@QEAAHHAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)
> blah blah blah
> {code}



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

[jira] [Updated] (THRIFT-3518) TConcurrentClientSyncInfo files were missing for Visual Studio


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

Xiaoshuang LU updated THRIFT-3518:
--
Description: 
$. thrift file
{code}
namespace cpp test

service TestService
{
i32 test(1:i32 data1, 2:string data2);
}
{code}

$. compile thrift file
{code}
thrift --strict --gen cpp --out . TestService.thrift
{code}

$. build with Visual Studio
{code}
SeverityCodeDescription Project FileLine
Error   LNK2019 unresolved external symbol "public: __cdecl 
apache::thrift::async::TConcurrentSendSentry::TConcurrentSendSentry(class 
apache::thrift::async::TConcurrentClientSyncInfo *)" 
(??0TConcurrentSendSentry@async@thrift@apache@@QEAA@PEAVTConcurrentClientSyncInfo@123@@Z)
 referenced in function "public: int __cdecl 
test::TestServiceConcurrentClient::send_test(int,class 
std::basic_string const &)" 
(?send_test@TestServiceConcurrentClient@test@@QEAAHHAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)

blah blah blah
{code}

> TConcurrentClientSyncInfo files were missing for Visual Studio
> --
>
> Key: THRIFT-3518
> URL: https://issues.apache.org/jira/browse/THRIFT-3518
> Project: Thrift
>  Issue Type: Bug
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>Priority: Blocker
> Fix For: 0.9.4
>
> Attachments: THRIFT-3518.patch
>
>
> $. thrift file
> {code}
> namespace cpp test
> service TestService
> {
> i32 test(1:i32 data1, 2:string data2);
> }
> {code}
> $. compile thrift file
> {code}
> thrift --strict --gen cpp --out . TestService.thrift
> {code}
> $. build with Visual Studio
> {code}
> Severity  CodeDescription Project FileLine
> Error LNK2019 unresolved external symbol "public: __cdecl 
> apache::thrift::async::TConcurrentSendSentry::TConcurrentSendSentry(class 
> apache::thrift::async::TConcurrentClientSyncInfo *)" 
> (??0TConcurrentSendSentry@async@thrift@apache@@QEAA@PEAVTConcurrentClientSyncInfo@123@@Z)
>  referenced in function "public: int __cdecl 
> test::TestServiceConcurrentClient::send_test(int,class 
> std::basic_string std::allocator > const &)" 
> (?send_test@TestServiceConcurrentClient@test@@QEAAHHAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)
> blah blah blah
> {code}



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

[jira] [Updated] (THRIFT-3518) TConcurrentClientSyncInfo files were missing for Visual Studio


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

Xiaoshuang LU updated THRIFT-3518:
--
Attachment: THRIFT-3518.patch

> TConcurrentClientSyncInfo files were missing for Visual Studio
> --
>
> Key: THRIFT-3518
> URL: https://issues.apache.org/jira/browse/THRIFT-3518
> Project: Thrift
>  Issue Type: Bug
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
>Priority: Blocker
> Fix For: 0.9.4
>
> Attachments: THRIFT-3518.patch
>
>




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

[jira] [Created] (THRIFT-3518) TConcurrentClientSyncInfo files were missing for Visual Studio

Xiaoshuang LU created THRIFT-3518:
-

 Summary: TConcurrentClientSyncInfo files were missing for Visual 
Studio
 Key: THRIFT-3518
 URL: https://issues.apache.org/jira/browse/THRIFT-3518
 Project: Thrift
  Issue Type: Bug
  Components: C++ - Library
Affects Versions: 0.9.3
Reporter: Xiaoshuang LU
Priority: Blocker
 Fix For: 0.9.4






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

[jira] [Commented] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations

2015-12-13 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15055269#comment-15055269
 ] 

Xiaoshuang LU commented on THRIFT-3481:
---

Hi [~nsuke] , thanks for your comments.  From my perspective, 
TSimpleMemoryTransport is a new introduced class and it will not cause any 
compatibility issues.

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Commented] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


[ 
https://issues.apache.org/jira/browse/THRIFT-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052009#comment-15052009
 ] 

Xiaoshuang LU commented on THRIFT-3481:
---

Lines from 477 to 496 in file 
https://github.com/apache/thrift/blob/master/lib/cpp/src/thrift/transport/TBufferTransports.h.

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Comment Edited] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


[ 
https://issues.apache.org/jira/browse/THRIFT-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052032#comment-15052032
 ] 

Xiaoshuang LU edited comment on THRIFT-3481 at 12/11/15 2:17 AM:
-

e.g.

{code}
// sufficiently large
char buffer[4096];

boost::shared_ptr transport{ new TMemoryBuffer(buffer, 4096, 
TMemoryBuffer::OBSERVE) };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

object.write(protocol.get());
{code}

We will get

{code}
terminate called after throwing an instance of 
'apache::thrift::transport::TTransportException'
  what():  Insufficient space in external MemoryBuffer
Aborted (core dumped)
{code}


was (Author: in-chief):
e.g.

{code}
// sufficiently large
char buffer[4096];

boost::shared_ptr transport{ new TMemoryBuffer(buffer, 1024, 
TMemoryBuffer::OBSERVE) };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

object.write(protocol.get());
{code}

We will get

{code}
terminate called after throwing an instance of 
'apache::thrift::transport::TTransportException'
  what():  Insufficient space in external MemoryBuffer
Aborted (core dumped)
{code}

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Comment Edited] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


[ 
https://issues.apache.org/jira/browse/THRIFT-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052032#comment-15052032
 ] 

Xiaoshuang LU edited comment on THRIFT-3481 at 12/11/15 2:16 AM:
-

e.g.

{code}
// sufficiently large
char buffer[4096];

boost::shared_ptr transport{ new TMemoryBuffer(buffer, 1024, 
TMemoryBuffer::OBSERVE) };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

object.write(protocol.get());
{code}

We will get

{code}
terminate called after throwing an instance of 
'apache::thrift::transport::TTransportException'
  what():  Insufficient space in external MemoryBuffer
Aborted (core dumped)
{code}


was (Author: in-chief):
{code}
// sufficiently large
char buffer[4096];

boost::shared_ptr transport{ new TMemoryBuffer(buffer, 1024, 
TMemoryBuffer::OBSERVE) };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

object.write(protocol.get());
{code}

We will get

{code}
terminate called after throwing an instance of 
'apache::thrift::transport::TTransportException'
  what():  Insufficient space in external MemoryBuffer
Aborted (core dumped)
{code}

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Commented] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


[ 
https://issues.apache.org/jira/browse/THRIFT-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052032#comment-15052032
 ] 

Xiaoshuang LU commented on THRIFT-3481:
---

{code}
// sufficiently large
char buffer[4096];

boost::shared_ptr transport{ new TMemoryBuffer(buffer, 1024, 
TMemoryBuffer::OBSERVE) };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

object.write(protocol.get());
{code}

We will get

{code}
terminate called after throwing an instance of 
'apache::thrift::transport::TTransportException'
  what():  Insufficient space in external MemoryBuffer
Aborted (core dumped)
{code}

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Updated] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


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

Xiaoshuang LU updated THRIFT-3481:
--
Attachment: (was: THRIFT-3481.patch)

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Updated] (THRIFT-3480) offer a simple approach to compute byte size of the serialized object


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

Xiaoshuang LU updated THRIFT-3480:
--
Attachment: THRIFT-3480.patch

> offer a simple approach to compute byte size of the serialized object
> -
>
> Key: THRIFT-3480
> URL: https://issues.apache.org/jira/browse/THRIFT-3480
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3480.patch
>
>
> Hi Thrift guys, I would like to propose a transport for computing byte size 
> of the serialized object.  Here is a example.
> {code}
> boost::shared_ptr transport{ new TWriteOnlyTransport 
> };
> boost::shared_ptr protocol{ new 
> TBinaryProtocol(transport) };
> size = object.write(protocol.get());
> {code}
> A write only transport can be written but never read.  It discards all data 
> written to it but reports that the write operation succeeded.



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

[jira] [Updated] (THRIFT-3480) offer a simple approach to compute byte size of the serialized object


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

Xiaoshuang LU updated THRIFT-3480:
--
Attachment: (was: THRIFT-3480.patch)

> offer a simple approach to compute byte size of the serialized object
> -
>
> Key: THRIFT-3480
> URL: https://issues.apache.org/jira/browse/THRIFT-3480
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
>
> Hi Thrift guys, I would like to propose a transport for computing byte size 
> of the serialized object.  Here is a example.
> {code}
> boost::shared_ptr transport{ new TWriteOnlyTransport 
> };
> boost::shared_ptr protocol{ new 
> TBinaryProtocol(transport) };
> size = object.write(protocol.get());
> {code}
> A write only transport can be written but never read.  It discards all data 
> written to it but reports that the write operation succeeded.



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

[jira] [Updated] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


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

Xiaoshuang LU updated THRIFT-3481:
--
Attachment: THRIFT-3481.patch

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Updated] (THRIFT-3480) offer a simple approach to compute byte size of the serialized object


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

Xiaoshuang LU updated THRIFT-3480:
--
Description: 
Hi Thrift guys, I would like to propose a transport for computing byte size of 
the serialized object.  Here is a example.

{code}
boost::shared_ptr transport{ new TWriteOnlyTransport };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

size = object.write(protocol.get());
{code}

A write only transport can be written but never read.  It discards all data 
written to it but reports that the write operation succeeded.  And the truth is 
that write function of this transport does nothing at all.

  was:
Hi Thrift guys, I would like to propose a transport for computing byte size of 
the serialized object.  Here is a example.

{code}
boost::shared_ptr transport{ new TWriteOnlyTransport };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

size = object.write(protocol.get());
{code}

A write only transport can be written but never read.  It discards all data 
written to it but reports that the write operation succeeded.


> offer a simple approach to compute byte size of the serialized object
> -
>
> Key: THRIFT-3480
> URL: https://issues.apache.org/jira/browse/THRIFT-3480
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3480.patch
>
>
> Hi Thrift guys, I would like to propose a transport for computing byte size 
> of the serialized object.  Here is a example.
> {code}
> boost::shared_ptr transport{ new TWriteOnlyTransport 
> };
> boost::shared_ptr protocol{ new 
> TBinaryProtocol(transport) };
> size = object.write(protocol.get());
> {code}
> A write only transport can be written but never read.  It discards all data 
> written to it but reports that the write operation succeeded.  And the truth 
> is that write function of this transport does nothing at all.



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

[jira] [Created] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations

Xiaoshuang LU created THRIFT-3481:
-

 Summary: introduce TSimpleMemoryTransport which wraps a customer 
owned memory chunk to conduct both read and write operations
 Key: THRIFT-3481
 URL: https://issues.apache.org/jira/browse/THRIFT-3481
 Project: Thrift
  Issue Type: New Feature
  Components: C++ - Library
Affects Versions: 0.9.3
Reporter: Xiaoshuang LU
 Fix For: 0.9.4


It would be great if there is a transport class which 1. does not need to care 
about the memory management, 2. is capable of both read and write operations.

TMemoryBuffer is very close to the requirements, but no data can be written to 
observed TMemoryBuffer as stated in the comments.



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

[jira] [Updated] (THRIFT-3481) introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to conduct both read and write operations


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

Xiaoshuang LU updated THRIFT-3481:
--
Attachment: THRIFT-3481.patch

> introduce TSimpleMemoryTransport which wraps a customer owned memory chunk to 
> conduct both read and write operations
> 
>
> Key: THRIFT-3481
> URL: https://issues.apache.org/jira/browse/THRIFT-3481
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3481.patch
>
>
> It would be great if there is a transport class which 1. does not need to 
> care about the memory management, 2. is capable of both read and write 
> operations.
> TMemoryBuffer is very close to the requirements, but no data can be written 
> to observed TMemoryBuffer as stated in the comments.



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

[jira] [Updated] (THRIFT-3480) offer a simple approach to compute byte size of the serialized object


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

Xiaoshuang LU updated THRIFT-3480:
--
Attachment: THRIFT-3480.patch

> offer a simple approach to compute byte size of the serialized object
> -
>
> Key: THRIFT-3480
> URL: https://issues.apache.org/jira/browse/THRIFT-3480
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3480.patch
>
>
> Hi Thrift guys, I would like to propose a transport for computing byte size 
> of the serialized object.  Here is a example.
> {{
> boost::shared_ptr transport{ new TWriteOnlyTransport 
> };
> boost::shared_ptr protocol{ new 
> TBinaryProtocol(transport) };
> size = object.write(protocol.get());
> }}
> A write only transport can be written but never read.  It discards all data 
> written to it but reports that the write operation succeeded.



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

[jira] [Updated] (THRIFT-3480) offer a simple approach to compute byte size of the serialized object


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

Xiaoshuang LU updated THRIFT-3480:
--
Description: 
Hi Thrift guys, I would like to propose a transport for computing byte size of 
the serialized object.  Here is a example.

{code}
boost::shared_ptr transport{ new TWriteOnlyTransport };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

size = object.write(protocol.get());
{code}

A write only transport can be written but never read.  It discards all data 
written to it but reports that the write operation succeeded.

  was:
Hi Thrift guys, I would like to propose a transport for computing byte size of 
the serialized object.  Here is a example.

{{
boost::shared_ptr transport{ new TWriteOnlyTransport };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

size = object.write(protocol.get());
}}

A write only transport can be written but never read.  It discards all data 
written to it but reports that the write operation succeeded.


> offer a simple approach to compute byte size of the serialized object
> -
>
> Key: THRIFT-3480
> URL: https://issues.apache.org/jira/browse/THRIFT-3480
> Project: Thrift
>  Issue Type: New Feature
>  Components: C++ - Library
>Affects Versions: 0.9.3
>Reporter: Xiaoshuang LU
> Fix For: 0.9.4
>
> Attachments: THRIFT-3480.patch
>
>
> Hi Thrift guys, I would like to propose a transport for computing byte size 
> of the serialized object.  Here is a example.
> {code}
> boost::shared_ptr transport{ new TWriteOnlyTransport 
> };
> boost::shared_ptr protocol{ new 
> TBinaryProtocol(transport) };
> size = object.write(protocol.get());
> {code}
> A write only transport can be written but never read.  It discards all data 
> written to it but reports that the write operation succeeded.



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

[jira] [Created] (THRIFT-3480) offer a simple approach to compute byte size of the serialized object

Xiaoshuang LU created THRIFT-3480:
-

 Summary: offer a simple approach to compute byte size of the 
serialized object
 Key: THRIFT-3480
 URL: https://issues.apache.org/jira/browse/THRIFT-3480
 Project: Thrift
  Issue Type: New Feature
  Components: C++ - Library
Affects Versions: 0.9.3
Reporter: Xiaoshuang LU
 Fix For: 0.9.4


Hi Thrift guys, I would like to propose a transport for computing byte size of 
the serialized object.  Here is a example.

{{
boost::shared_ptr transport{ new TWriteOnlyTransport };
boost::shared_ptr protocol{ new TBinaryProtocol(transport) 
};

size = object.write(protocol.get());
}}

A write only transport can be written but never read.  It discards all data 
written to it but reports that the write operation succeeded.



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

[jira] [Updated] (THRIFT-3320) TMessages of multiplexed service responses of should include service names

2015-09-10 Thread Xiaoshuang LU (JIRA)


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

Xiaoshuang LU updated THRIFT-3320:
--
Component/s: Python - Library
 C++ - Library
 Issue Type: Story  (was: Wish)

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Story
>  Components: C++ - Library, Java - Library, Python - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>




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

[jira] [Commented] (THRIFT-3320) TMessages of multiplexed service responses of should include service names


[ 
https://issues.apache.org/jira/browse/THRIFT-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737998#comment-14737998
 ] 

Xiaoshuang LU commented on THRIFT-3320:
---

Hi Jens, thanks for your comments.

Suppose clients use "TMultiplexedProtocol"s while servers run 
"TMultiplexedProcessor"s. The "TMessage"s encapsulated in requests appear like 
(name = serviceName:procedureName, type = call, seqid = blah_blah_blah). 
However response "TMessage"s lack serviceName in their name fields. I propose 
that both request and response "TMessage"s shall have the same format except 
their type fields.

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Wish
>  Components: Java - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
>




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

[jira] [Commented] (THRIFT-3320) TMessages of multiplexed service responses of should include service names


[ 
https://issues.apache.org/jira/browse/THRIFT-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738014#comment-14738014
 ] 

Xiaoshuang LU commented on THRIFT-3320:
---

Hi [~jensg], it seems that asynchronous processors are not capable of 
multiplexed services.  Am I correct?

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Wish
>  Components: Java - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
>




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

[jira] [Commented] (THRIFT-3013) make thrift compiler accept a list of input files


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738185#comment-14738185
 ] 

Xiaoshuang LU commented on THRIFT-3013:
---

Hi [~jfarrell], I prefer to a whole option parser because the less changes we 
make, the less effects we need when rebasing to the new code.

> make thrift compiler accept a list of input files
> -
>
> Key: THRIFT-3013
> URL: https://issues.apache.org/jira/browse/THRIFT-3013
> Project: Thrift
>  Issue Type: New Feature
>  Components: Compiler (General)
>Affects Versions: 0.9.2
>Reporter: Xiaoshuang LU
>Assignee: Roger Meier
> Attachments: THRIFT-3013.v4.patch
>
>
> At present, customers could only specify one input file to thrift compiler.  
> There are maybe two approaches to support multiple input files.
> Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
> can borrow code from GUN's getopt_long.
> Approach 2: Offer users a maven plugin which can help them to iterate through 
> a list of input files.



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

[jira] [Comment Edited] (THRIFT-3320) TMessages of multiplexed service responses of should include service names


[ 
https://issues.apache.org/jira/browse/THRIFT-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14737998#comment-14737998
 ] 

Xiaoshuang LU edited comment on THRIFT-3320 at 9/10/15 5:22 AM:


Hi Jens, thanks for your comments.

Suppose a  scenario, let's say, clients use "TMultiplexedProtocol"s while 
servers run "TMultiplexedProcessor"s. The "TMessage"s encapsulated in requests 
appear like (name = serviceName:procedureName, type = call, seqid = 
blah_blah_blah). However response "TMessage"s lack serviceName in their name 
fields. I propose that both request and response "TMessage"s shall have the 
same values except their type fields.


was (Author: in-chief):
Hi Jens, thanks for your comments.

Suppose clients use "TMultiplexedProtocol"s while servers run 
"TMultiplexedProcessor"s. The "TMessage"s encapsulated in requests appear like 
(name = serviceName:procedureName, type = call, seqid = blah_blah_blah). 
However response "TMessage"s lack serviceName in their name fields. I propose 
that both request and response "TMessage"s shall have the same format except 
their type fields.

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Wish
>  Components: Java - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>




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

[jira] [Updated] (THRIFT-3320) TMessages of multiplexed service responses of should include service names


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

Xiaoshuang LU updated THRIFT-3320:
--
Attachment: THRIFT-3320.patch

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Wish
>  Components: Java - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>




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

[jira] [Updated] (THRIFT-3320) TMessages of multiplexed service responses of should include service names


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

Xiaoshuang LU updated THRIFT-3320:
--
Flags: Patch

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Wish
>  Components: Java - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>




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

[jira] [Created] (THRIFT-3320) TMessages of multiplexed service responses of should have service names

2015-09-08 Thread Xiaoshuang LU (JIRA)

Xiaoshuang LU created THRIFT-3320:
-

 Summary: TMessages of multiplexed service responses of should have 
service names
 Key: THRIFT-3320
 URL: https://issues.apache.org/jira/browse/THRIFT-3320
 Project: Thrift
  Issue Type: Bug
  Components: Java - Library
Affects Versions: 0.9.2, 0.9.1, 0.9
Reporter: Xiaoshuang LU






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

[jira] [Updated] (THRIFT-3320) TMessages of multiplexed service responses of should include service names

2015-09-08 Thread Xiaoshuang LU (JIRA)


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

Xiaoshuang LU updated THRIFT-3320:
--
Summary: TMessages of multiplexed service responses of should include 
service names  (was: TMessages of multiplexed service responses of should have 
service names)

> TMessages of multiplexed service responses of should include service names
> --
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
>  Issue Type: Bug
>  Components: Java - Library
>Affects Versions: 0.9, 0.9.1, 0.9.2
>Reporter: Xiaoshuang LU
>




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

[jira] [Updated] (THRIFT-3298) thrift endian converters may conflict with other libraries


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

Xiaoshuang LU updated THRIFT-3298:
--
Attachment: THRIFT-3298.patch

 thrift endian converters may conflict with other libraries
 --

 Key: THRIFT-3298
 URL: https://issues.apache.org/jira/browse/THRIFT-3298
 Project: Thrift
  Issue Type: Improvement
  Components: C++ - Library
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
 Fix For: 0.9.3

 Attachments: THRIFT-3298.patch


 Thrift C++ library offers some endian converters in TProtocol.h, e.g. ntohll, 
 htonll, and etc.  Some other libraries may also have these kinds of 
 converters, such as ZooKeeper.  And if we include TProtocol.h prior to 
 zookeeper.h, zookeeper's htonll will be replaced by the thrift macros 
 mentioned above.  Consequently, I propose that we may add prefix THRIFT_ to 
 all these converters.



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

[jira] [Updated] (THRIFT-3298) thrift endian converters may conflict with other libraries


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

Xiaoshuang LU updated THRIFT-3298:
--
Patch Info: Patch Available

 thrift endian converters may conflict with other libraries
 --

 Key: THRIFT-3298
 URL: https://issues.apache.org/jira/browse/THRIFT-3298
 Project: Thrift
  Issue Type: Improvement
  Components: C++ - Library
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
 Fix For: 0.9.3

 Attachments: THRIFT-3298.patch


 Thrift C++ library offers some endian converters in TProtocol.h, e.g. ntohll, 
 htonll, and etc.  Some other libraries may also have these kinds of 
 converters, such as ZooKeeper.  And if we include TProtocol.h prior to 
 zookeeper.h, zookeeper's htonll will be replaced by the thrift macros 
 mentioned above.  Consequently, I propose that we may add prefix THRIFT_ to 
 all these converters.



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

[jira] [Created] (THRIFT-3298) thrift endian converter may conflict with other libraries

Xiaoshuang LU created THRIFT-3298:
-

 Summary: thrift endian converter may conflict with other libraries
 Key: THRIFT-3298
 URL: https://issues.apache.org/jira/browse/THRIFT-3298
 Project: Thrift
  Issue Type: Improvement
  Components: C++ - Library
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
 Fix For: 0.9.3


Thrift C++ library offers some endian converters in TProtocol.h, e.g. ntohll, 
htonll, and etc.  Some other libraries may also have these kinds of converters, 
such as ZooKeeper.  And if we include TProtocol.h in prior to zookeeper.h, 
zookeeper's htonll will be replaced by the thrift macros.  Consequently, I 
propose that we may add prefix THRIFT_ to these converters.



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

[jira] [Updated] (THRIFT-3298) thrift endian converters may conflict with other libraries

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

Xiaoshuang LU updated THRIFT-3298:
--
Description: Thrift C++ library offers some endian converters in
TProtocol.h, e.g. ntohll, htonll, and etc. Some other libraries may also have
these kinds of converters, such as ZooKeeper. And if we include TProtocol.h
prior to zookeeper.h, zookeeper's htonll will be replaced by the thrift macros
mentioned above. Consequently, I propose that we may add prefix THRIFT_ to
all these converters. (was: Thrift C++ library offers some endian converters
in TProtocol.h, e.g. ntohll, htonll, and etc. Some other libraries may also
have these kinds of converters, such as ZooKeeper. And if we include
TProtocol.h in prior to zookeeper.h, zookeeper's htonll will be replaced by the
thrift macros. Consequently, I propose that we may add prefix THRIFT_ to
these converters.)
Summary: thrift endian converters may conflict with other libraries
(was: thrift endian converter may conflict with other libraries)

thrift endian converters may conflict with other libraries
--

Key: THRIFT-3298
URL: https://issues.apache.org/jira/browse/THRIFT-3298
Project: Thrift
Issue Type: Improvement
Components: C++ - Library
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Fix For: 0.9.3

Thrift C++ library offers some endian converters in TProtocol.h, e.g. ntohll,
htonll, and etc. Some other libraries may also have these kinds of
converters, such as ZooKeeper. And if we include TProtocol.h prior to
zookeeper.h, zookeeper's htonll will be replaced by the thrift macros
mentioned above. Consequently, I propose that we may add prefix THRIFT_ to
all these converters.

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

[jira] [Created] (THRIFT-3181) create TQueuedServer to improve performance

2015-06-07 Thread Xiaoshuang LU (JIRA)

Xiaoshuang LU created THRIFT-3181:
-

 Summary: create TQueuedServer to improve performance
 Key: THRIFT-3181
 URL: https://issues.apache.org/jira/browse/THRIFT-3181
 Project: Thrift
  Issue Type: Sub-task
  Components: Java - Library
Reporter: Xiaoshuang LU


A TQueuedServer receives RPC requests and adds them into a queue for execution 
by threads.



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

[jira] [Updated] (THRIFT-3181) create TQueuedServer to improve performance

2015-06-07 Thread Xiaoshuang LU (JIRA)


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

Xiaoshuang LU updated THRIFT-3181:
--
Description: 
A TQueuedServer receives RPC requests and adds them into queues for execution 
by threads.

References
[1]. http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/

  was:
A TQueuedServer receives RPC requests and adds them into a queue for execution 
by threads.

References
[1]. http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/


 create TQueuedServer to improve performance
 ---

 Key: THRIFT-3181
 URL: https://issues.apache.org/jira/browse/THRIFT-3181
 Project: Thrift
  Issue Type: Sub-task
  Components: Java - Library
Reporter: Xiaoshuang LU

 A TQueuedServer receives RPC requests and adds them into queues for execution 
 by threads.
 References
 [1]. http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/



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

[jira] [Updated] (THRIFT-3181) create TQueuedServer to improve performance

2015-06-07 Thread Xiaoshuang LU (JIRA)


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

Xiaoshuang LU updated THRIFT-3181:
--
Description: 
A TQueuedServer receives RPC requests and adds them into queues for processing 
by threads.

References
[1]. http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/

  was:
A TQueuedServer receives RPC requests and adds them into queues for execution 
by threads.

References
[1]. http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/


 create TQueuedServer to improve performance
 ---

 Key: THRIFT-3181
 URL: https://issues.apache.org/jira/browse/THRIFT-3181
 Project: Thrift
  Issue Type: Sub-task
  Components: Java - Library
Reporter: Xiaoshuang LU

 A TQueuedServer receives RPC requests and adds them into queues for 
 processing by threads.
 References
 [1]. http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/



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

[jira] [Commented] (THRIFT-3127) switch -recurse to --recurse and reserve -r

2015-05-13 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541945#comment-14541945
 ] 

Xiaoshuang LU commented on THRIFT-3127:
---

This ticket is blocked by THRIFT-3013.

 switch -recurse to --recurse and reserve -r
 ---

 Key: THRIFT-3127
 URL: https://issues.apache.org/jira/browse/THRIFT-3127
 Project: Thrift
  Issue Type: Improvement
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU

 we may need to switch {code}-recurse{code} to {code}--recurse{code},
 and reserve {code}-r{code} since it is the standard behavior of command line 
 parameter processing.



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

[jira] [Updated] (THRIFT-3032) performance improvement for TBaseProcessor

2015-05-09 Thread Xiaoshuang LU (JIRA)


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

Xiaoshuang LU updated THRIFT-3032:
--
Description: A TBaseProcessor uses a map to store all the methods of a 
service.  I suggest that an array or ArrayList should be used. Methods can be 
identified by indices for which the worst-case complexity is O(1) while 
computing hash code for a string is not.  To achieve this goal, we may tell the 
compiler to generate a enumeration constant list of all the methods per 
service.  The ordinals of the enumeration constants need to be package into the 
messages rather than the name of methods.  And in theory network overhead 
should be reduced additionally.  (was: A TBaseProcessor uses a map to store 
all the methods of a service.  I suggest that a array or ArrayList should be 
used. Methods can be identified by indices for which the worst-case complexity 
is O(1) while computing hash code for a string is not.  To achieve this goal, 
we may tell the compiler to generate a enumeration constant list of all the 
methods per service.  The ordinals of the enumeration constants need to be 
package into the messages rather than the name of methods.  And in theory 
network overhead should be reduced additionally.)

 performance improvement for TBaseProcessor
 --

 Key: THRIFT-3032
 URL: https://issues.apache.org/jira/browse/THRIFT-3032
 Project: Thrift
  Issue Type: Story
  Components: Java - Library
Affects Versions: 0.9.1, 0.9.2
Reporter: Xiaoshuang LU

 A TBaseProcessor uses a map to store all the methods of a service.  I 
 suggest that an array or ArrayList should be used. Methods can be 
 identified by indices for which the worst-case complexity is O(1) while 
 computing hash code for a string is not.  To achieve this goal, we may tell 
 the compiler to generate a enumeration constant list of all the methods per 
 service.  The ordinals of the enumeration constants need to be package into 
 the messages rather than the name of methods.  And in theory network overhead 
 should be reduced additionally.



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

[jira] [Updated] (THRIFT-3013) make thrift compiler accept a list of input files

2015-05-09 Thread Xiaoshuang LU (JIRA)

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

Xiaoshuang LU updated THRIFT-3013:
--
Description:
At present, customers could only specify one input file to thrift compiler.
There are maybe two approaches to support multiple input files.

Approach 1: Improve the option parser in compiler/cpp/src/main.cc. Maybe we
can borrow code from GUN's getopt_long.

Approach 2: Offer users a maven plugin which can help them to iterate through a
list of input files.

was:
At present, customer could specify one input file to the thrift compiler.
There are maybe two approaches to support multiple input files.

Approach 1: Improve the option parser in compiler/cpp/src/main.cc. Maybe we
can borrow code from GUN's getopt_long.

Approach 2: Offer users a maven plugin which can help them to iterate through a
list of input files.

make thrift compiler accept a list of input files
-

Key: THRIFT-3013
URL: https://issues.apache.org/jira/browse/THRIFT-3013
Project: Thrift
Issue Type: New Feature
Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
Fix For: 0.9.3

Attachments: THRIFT-3013.v4.patch

At present, customers could only specify one input file to thrift compiler.
There are maybe two approaches to support multiple input files.
Approach 1: Improve the option parser in compiler/cpp/src/main.cc. Maybe we
can borrow code from GUN's getopt_long.
Approach 2: Offer users a maven plugin which can help them to iterate through
a list of input files.

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

[jira] [Created] (THRIFT-3127) switch -recurse to --recurse and reserve -r

2015-05-05 Thread Xiaoshuang LU (JIRA)

Xiaoshuang LU created THRIFT-3127:
-

 Summary: switch -recurse to --recurse and reserve -r
 Key: THRIFT-3127
 URL: https://issues.apache.org/jira/browse/THRIFT-3127
 Project: Thrift
  Issue Type: Improvement
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU


we may need to switch {code}-recurse{code} to {code}--recurse{code},
and reserve {code}-r{code} since it is the standard behavior of command line 
parameter processing.



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

[jira] [Comment Edited] (THRIFT-3013) make thrift compiler accept a list of input files

2015-05-05 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528407#comment-14528407
 ] 

Xiaoshuang LU edited comment on THRIFT-3013 at 5/5/15 1:20 PM:
---

Hi [~roger.meier], new ticket has been created 
([https://issues.apache.org/jira/browse/THRIFT-3127]).  And would you please 
commit this patch to trunk if everything is okay to you?  Thanks.


was (Author: in-chief):
Hi [~roger.meier], new ticket 
[https://issues.apache.org/jira/browse/THRIFT-3127] has been created.  And 
would you please commit this patch to trunk if everything is okay to you?  
Thanks.

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Fix For: 0.9.3

 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Commented] (THRIFT-3013) make thrift compiler accept a list of input files

2015-05-05 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528407#comment-14528407
 ] 

Xiaoshuang LU commented on THRIFT-3013:
---

Hi [~roger.meier], new ticket 
[https://issues.apache.org/jira/browse/THRIFT-3127] has been created.  And 
would you please commit this patch to trunk if everything is okay to you?  
Thanks.

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Fix For: 0.9.3

 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Commented] (THRIFT-3013) make thrift compiler accept a list of input files

2015-05-03 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526139#comment-14526139
 ] 

Xiaoshuang LU commented on THRIFT-3013:
---

Hi [~roger.meier], thanks for your comments.  What about switching -recurse 
to --recurse in another ticket?

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Fix For: 0.9.3

 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Comment Edited] (THRIFT-3013) make thrift compiler accept a list of input files

2015-05-03 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526139#comment-14526139
 ] 

Xiaoshuang LU edited comment on THRIFT-3013 at 5/4/15 1:25 AM:
---

Hi [~roger.meier], thanks for your comments.  What about switching 
{code}-recurse{code} to {code}--recurse{code} in another ticket?


was (Author: in-chief):
Hi [~roger.meier], thanks for your comments.  What about switching -recurse 
to --recurse in another ticket?

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Fix For: 0.9.3

 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Commented] (THRIFT-3013) make thrift compiler accept a list of input files

2015-04-21 Thread Xiaoshuang LU (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14504945#comment-14504945
 ] 

Xiaoshuang LU commented on THRIFT-3013:
---

Hi [~roger.meier], would you mind trying the new patch? Thank you.

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Updated] (THRIFT-3013) make thrift compiler accept a list of input files


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

Xiaoshuang LU updated THRIFT-3013:
--
Attachment: (was: THRIFT-3013.v3.patch)

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Updated] (THRIFT-3013) make thrift compiler accept a list of input files


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

Xiaoshuang LU updated THRIFT-3013:
--
Attachment: (was: THRIFT-3013.patch)

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.v3.patch, THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Comment Edited] (THRIFT-3013) make thrift compiler accept a list of input files


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14499756#comment-14499756
 ] 

Xiaoshuang LU edited comment on THRIFT-3013 at 4/17/15 12:52 PM:
-

Hi [~roger.meier], I have migrated the patch from getopt_long to 
getopt_long_only.  The main differences between them are described as follows.

{quote}
The getopt_long_only() function behaves identically to getopt_long() with
the exception that long options may start with - in addition to --.
If an option starting with - does not match a long option but does
match a single-character option, the single-character option is returned.
{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html


was (Author: in-chief):
Hi [~roger.meier], I have migrated the patch from getopt_long to 
getopt_long_only.  The main differences between them are described as follows.

{quote}
The getopt_long_only() function behaves identically to getopt_long() with
the exception that long options may start with `-' in addition to `--'.
If an option starting with `-' does not match a long option but does
match a single-character option, the single-character option is returned.
{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Updated] (THRIFT-3013) make thrift compiler accept a list of input files


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

Xiaoshuang LU updated THRIFT-3013:
--
Attachment: THRIFT-3013.v4.patch

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Created] (THRIFT-3102) could not make check for Go Library

Xiaoshuang LU created THRIFT-3102:
-

 Summary: could not make check for Go Library
 Key: THRIFT-3102
 URL: https://issues.apache.org/jira/browse/THRIFT-3102
 Project: Thrift
  Issue Type: Bug
  Components: Go - Library
Affects Versions: 0.9.2
 Environment: OS: CentOS 7.1 x86_64
golang: 1.4
Reporter: Xiaoshuang LU


steps to reproduce

1. ./bootstrap.sh
2. ./configure --with-boost=/software/boost_1_57_0 
--prefix=/home/username/software/thrift-master 
--with-libevent=/software/libevent-2.0.22 --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --with-go 
--without-haxe --without-d --without-cpp
3. make
4. make check

grep -v list.*map.*list.*map ../../../test/ThriftTest.thrift | grep -v 
'setInsanity'  ThriftTest.thrift
../../../compiler/cpp/thrift  -r IncludesTest.thrift
No output language(s) specified
Usage: thrift [options] file

Use thrift -help for a list of options
make[3]: *** [gopath] Error 1

make check still does work even after I modify lib/go/test/Makefile.am (add 
--gen go)



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

[jira] [Updated] (THRIFT-3013) make thrift compiler accept a list of input files


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

Xiaoshuang LU updated THRIFT-3013:
--
Attachment: (was: THRIFT-3013.v4.patch)

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier

 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Issue Comment Deleted] (THRIFT-3013) make thrift compiler accept a list of input files


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

Xiaoshuang LU updated THRIFT-3013:
--
Comment: was deleted

(was: Hi [~roger.meier], I have migrate the patch from getopt_long to 
getopt_long_only.  The main difference between is that {quote}The 
getopt_long_only() function behaves identically to getopt_long() with
 the exception that long options may start with `-' in addition to `--'.
 If an option starting with `-' does not match a long option but does
 match a single-character option, the single-character option is 
returned.{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html)

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier

 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Comment Edited] (THRIFT-3013) make thrift compiler accept a list of input files


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14499756#comment-14499756
 ] 

Xiaoshuang LU edited comment on THRIFT-3013 at 4/17/15 12:49 PM:
-

Hi [~roger.meier], I have migrated the patch from getopt_long to 
getopt_long_only.  The main differences between them are described as follows.

{quote}
The getopt_long_only() function behaves identically to getopt_long() with
the exception that long options may start with `-' in addition to `--'.
If an option starting with `-' does not match a long option but does
match a single-character option, the single-character option is returned.
{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html


was (Author: in-chief):
Hi [~roger.meier], I have migrate the patch from getopt_long to 
getopt_long_only.  The main difference between is that {quote}The 
getopt_long_only() function behaves identically to getopt_long() with
 the exception that long options may start with `-' in addition to `--'.
 If an option starting with `-' does not match a long option but does
 match a single-character option, the single-character option is 
returned.{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier

 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Comment Edited] (THRIFT-3013) make thrift compiler accept a list of input files


[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14499756#comment-14499756
 ] 

Xiaoshuang LU edited comment on THRIFT-3013 at 4/17/15 12:54 PM:
-

Hi [~roger.meier], I have migrated the patch from getopt_long to 
getopt_long_only.  The main differences between them are described as follows.

{quote}
The getopt_long_only() function behaves identically to getopt_long() with
the exception that long options may start with '-' in addition to '--'.
If an option starting with '-' does not match a long option but does
match a single-character option, the single-character option is returned.
{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html


was (Author: in-chief):
Hi [~roger.meier], I have migrated the patch from getopt_long to 
getopt_long_only.  The main differences between them are described as follows.

{quote}
The getopt_long_only() function behaves identically to getopt_long() with
the exception that long options may start with - in addition to --.
If an option starting with - does not match a long option but does
match a single-character option, the single-character option is returned.
{quote}

References:
1. https://www.freebsd.org/cgi/man.cgi?getopt_long(3)
2. http://www.gnu.org/software/libc/manual/html_node/Getopt-Long-Options.html

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Updated] (THRIFT-3013) make thrift compiler accept a list of input files


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

Xiaoshuang LU updated THRIFT-3013:
--
Attachment: THRIFT-3013.v4.patch

 make thrift compiler accept a list of input files
 -

 Key: THRIFT-3013
 URL: https://issues.apache.org/jira/browse/THRIFT-3013
 Project: Thrift
  Issue Type: New Feature
  Components: Compiler (General)
Affects Versions: 0.9.2
Reporter: Xiaoshuang LU
Assignee: Roger Meier
 Attachments: THRIFT-3013.patch, THRIFT-3013.v2.patch, 
 THRIFT-3013.v3.patch, THRIFT-3013.v4.patch


 At present, customer could specify one input file to the thrift compiler.  
 There are maybe two approaches to support multiple input files.
 Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
 can borrow code from GUN's getopt_long.
 Approach 2: Offer users a maven plugin which can help them to iterate through 
 a list of input files.



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

[jira] [Updated] (THRIFT-3102) could not make check for Go Library


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

Xiaoshuang LU updated THRIFT-3102:
--
Description: 
steps to reproduce

1. ./bootstrap.sh
2. ./configure --with-boost=/software/boost_1_57_0 
--prefix=/home/username/software/thrift-master 
--with-libevent=/software/libevent-2.0.22 --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --with-go 
--without-haxe --without-d --without-cpp
3. make
4. make check

{quote}
grep -v list.*map.*list.*map ../../../test/ThriftTest.thrift | grep -v 
'setInsanity'  ThriftTest.thrift
../../../compiler/cpp/thrift  -r IncludesTest.thrift
No output language(s) specified
Usage: thrift [options] file

Use thrift -help for a list of options
make[3]: *** [gopath] Error 1
{quote}

make check still does not work even after I modify lib/go/test/Makefile.am (add 
--gen go).

{quote}
GOPATH=`pwd`/gopath /software/go-1.4/bin/go build \
includestest \
binarykeytest \
servicestest \
typedeffieldtest \
refannotationfieldstest \
errortest   \
namestest \
initialismstest
can't load package: package includestest: cannot find package includestest in 
any of:
/software/go-1.4/src/includestest (from $GOROOT)
/home/username/workshop/thrift-go/lib/go/test/gopath/src/includestest 
(from $GOPATH)
can't load package: package binarykeytest: cannot find package binarykeytest 
in any of:
/software/go-1.4/src/binarykeytest (from $GOROOT)
/home/username/workshop/thrift-go/lib/go/test/gopath/src/binarykeytest 
(from $GOPATH)
can't load package: package servicestest: cannot find package servicestest in 
any of:
/software/go-1.4/src/servicestest (from $GOROOT)
/home/username/workshop/thrift-go/lib/go/test/gopath/src/servicestest 
(from $GOPATH)
can't load package: package typedeffieldtest: cannot find package 
typedeffieldtest in any of:
/software/go-1.4/src/typedeffieldtest (from $GOROOT)

/home/username/workshop/thrift-go/lib/go/test/gopath/src/typedeffieldtest (from 
$GOPATH)
can't load package: package refannotationfieldstest: cannot find package 
refannotationfieldstest in any of:
/software/go-1.4/src/refannotationfieldstest (from $GOROOT)

/home/username/workshop/thrift-go/lib/go/test/gopath/src/refannotationfieldstest
 (from $GOPATH)
can't load package: package errortest: cannot find package errortest in any 
of:
/software/go-1.4/src/errortest (from $GOROOT)
/home/username/workshop/thrift-go/lib/go/test/gopath/src/errortest 
(from $GOPATH)
can't load package: package namestest: cannot find package namestest in any 
of:
/software/go-1.4/src/namestest (from $GOROOT)
/home/username/workshop/thrift-go/lib/go/test/gopath/src/namestest 
(from $GOPATH)
can't load package: package initialismstest: cannot find package 
initialismstest in any of:
/software/go-1.4/src/initialismstest (from $GOROOT)

/home/username/workshop/thrift-go/lib/go/test/gopath/src/initialismstest (from 
$GOPATH)
make[3]: *** [check] Error 1
{quote}

  was:
steps to reproduce

1. ./bootstrap.sh
2. ./configure --with-boost=/software/boost_1_57_0 
--prefix=/home/username/software/thrift-master 
--with-libevent=/software/libevent-2.0.22 --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --with-go 
--without-haxe --without-d --without-cpp
3. make
4. make check

grep -v list.*map.*list.*map ../../../test/ThriftTest.thrift | grep -v 
'setInsanity'  ThriftTest.thrift
../../../compiler/cpp/thrift  -r IncludesTest.thrift
No output language(s) specified
Usage: thrift [options] file

Use thrift -help for a list of options
make[3]: *** [gopath] Error 1

make check still does work even after I modify lib/go/test/Makefile.am (add 
--gen go)


 could not make check for Go Library
 ---

 Key: THRIFT-3102
 URL: https://issues.apache.org/jira/browse/THRIFT-3102
 Project: Thrift
  Issue Type: Bug
  Components: Go - Library
Affects Versions: 0.9.2
 Environment: OS: CentOS 7.1 x86_64
 golang: 1.4
Reporter: Xiaoshuang LU

 steps to reproduce
 1. ./bootstrap.sh
 2. ./configure --with-boost=/software/boost_1_57_0 
 --prefix=/home/username/software/thrift-master 
 --with-libevent=/software/libevent-2.0.22 --without-qt4 --without-qt5 
 --without-c_glib

[jira] [Updated] (THRIFT-3102) could not make check for Go Library


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

Xiaoshuang LU updated THRIFT-3102:
--
Description: 
steps to reproduce

1. ./bootstrap.sh
2. ./configure --with-boost=/software/boost_1_57_0 
--prefix=/home/username/software/thrift-master 
--with-libevent=/software/libevent-2.0.22 --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --with-go 
--without-haxe --without-d --without-cpp
3. make
4. make check

{quote}
grep -v list.*map.*list.*map ../../../test/ThriftTest.thrift | grep -v 
'setInsanity'  ThriftTest.thrift
../../../compiler/cpp/thrift  -r IncludesTest.thrift
No output language(s) specified
Usage: thrift [options] file

Use thrift -help for a list of options
make[3]: *** [gopath] Error 1
{quote}

make check still does not work even after I modify lib/go/test/Makefile.am 
(adding --gen go).

{quote}
GOPATH=`pwd`/gopath /software/go-1.4/bin/go build \
includestest \
binarykeytest \
servicestest \
typedeffieldtest \
refannotationfieldstest \
errortest   \
namestest \
initialismstest
can't load package: package includestest: cannot find package includestest in 
any of:
/software/go-1.4/src/includestest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/includestest (from $GOPATH)
can't load package: package binarykeytest: cannot find package binarykeytest 
in any of:
/software/go-1.4/src/binarykeytest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/binarykeytest (from $GOPATH)
can't load package: package servicestest: cannot find package servicestest in 
any of:
/software/go-1.4/src/servicestest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/servicestest (from $GOPATH)
can't load package: package typedeffieldtest: cannot find package 
typedeffieldtest in any of:
/software/go-1.4/src/typedeffieldtest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/typedeffieldtest (from 
$GOPATH)
can't load package: package refannotationfieldstest: cannot find package 
refannotationfieldstest in any of:
/software/go-1.4/src/refannotationfieldstest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/refannotationfieldstest 
(from $GOPATH)
can't load package: package errortest: cannot find package errortest in any 
of:
/software/go-1.4/src/errortest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/errortest (from $GOPATH)
can't load package: package namestest: cannot find package namestest in any 
of:
/software/go-1.4/src/namestest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/namestest (from $GOPATH)
can't load package: package initialismstest: cannot find package 
initialismstest in any of:
/software/go-1.4/src/initialismstest (from $GOROOT)
~/workshop/thrift-go/lib/go/test/gopath/src/initialismstest (from 
$GOPATH)
make[3]: *** [check] Error 1
{quote}

  was:
steps to reproduce

1. ./bootstrap.sh
2. ./configure --with-boost=/software/boost_1_57_0 
--prefix=/home/username/software/thrift-master 
--with-libevent=/software/libevent-2.0.22 --without-qt4 --without-qt5 
--without-c_glib --without-csharp --without-java --without-erlang 
--without-nodejs --without-lua --without-python --without-perl --without-php 
--without-php_extension --without-ruby --without-haskell --with-go 
--without-haxe --without-d --without-cpp
3. make
4. make check

{quote}
grep -v list.*map.*list.*map ../../../test/ThriftTest.thrift | grep -v 
'setInsanity'  ThriftTest.thrift
../../../compiler/cpp/thrift  -r IncludesTest.thrift
No output language(s) specified
Usage: thrift [options] file

Use thrift -help for a list of options
make[3]: *** [gopath] Error 1
{quote}

make check still does not work even after I modify lib/go/test/Makefile.am 
(adding --gen go).

{quote}
GOPATH=`pwd`/gopath /software/go-1.4/bin/go build \
includestest \
binarykeytest \
servicestest \
typedeffieldtest \
refannotationfieldstest \
errortest   \
namestest \
initialismstest
can't load package: package includestest: cannot find package includestest in 
any of:
/software/go-1.4/src/includestest (from $GOROOT)
/home/username/workshop/thrift-go/lib/go/test/gopath/src/includestest 
(from $GOPATH)
can't load package: package binarykeytest: cannot find package binarykeytest 
in any of:

[jira] [Updated] (THRIFT-3102) could not make check for Go Library