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

Randy Abernethy commented on THRIFT-2192:
-----------------------------------------

There are two other recent issue on the Centos (v6.5 86_x64) front. 

- The C++ lib fails to build due to Recursive_types.cpp. 
- The Lua lib also fails to build due to luasocket.c (Lua and Python always 
configure). 

The C++ lib appears to fail as a result of the default gcc/g++ 4.4.7 and Boost 
1.55 combination. You can build the C++ lib using the RHEL software collections 
utilities with the 4.7 compiler. I haven't debugged the Lua compile (it does 
not build even with gcc 4.7 on Centos 6.5).

With a bit of work we could get both of these to compile with gcc 4.4.7 on a 
plain vanilla Centos 6.5 box with nothing but base repos. In a perfect world 
we'd test on Centos, Ubuntu, OSX and Windows.

> autotools on Redhat based systems
> ---------------------------------
>
>                 Key: THRIFT-2192
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2192
>             Project: Thrift
>          Issue Type: Bug
>          Components: Build Process
>            Reporter: Hiroaki Kawai
>            Assignee: Jake Farrell
>              Labels: patch
>         Attachments: 0001-Support-for-autotools-on-Redhat-based-systems.patch
>
>
> It seems that thirft has been tested on ubuntu ( 
> https://builds.apache.org/job/Thrift/ ), but I could not run bootstrap on 
> Fedora.
> Because of automake 1.12 backward incompatibility, the Makefile.am in 
> compiler/cpp has been troublesome. I could create a workaround for it. The 
> patch was tested on CentOS 6.4 and Fedora 18 with command : `./bootstrap.sh 
> && ./configure && make && make dist`
> From the discussion of https://issues.apache.org/jira/browse/THRIFT-646 , 
> autoconf target was set to 2.65. On the other hand, CentOS 6.4 has 2.63 with 
> erlang patched. So I think it is safe to lower it to 2.63 here.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to