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

Anthony Molinaro commented on THRIFT-649:
-----------------------------------------

I'm okay with this patch being dropped.  Once cassandra is using a numbered 
release, and not an svn revision, my need to build from bootstrap myself will 
go away and I can rejigger my system for building rpms to build from the 
numbered release.  Until then I can keep applying these patches myself.  
(although you used to have quite a few folks who would run bootstrap.sh and get 
into an odd state because autoconf 2.59 is still very prevalent in production 
systems, so having something which works for both older and newer versions is 
pretty cool.  If you don't like the different way the AC_TYPE_INT16_T work in 
my patch, an alternate would be to grab the macros from 2.61 and put them in an 
acsite.m4 file which you include, however, I wasn't sure of the licensing of 
the macros, so didn't take that approach).

> Java documentation is installed in the wrong place when using autoconf 2.59
> ---------------------------------------------------------------------------
>
>                 Key: THRIFT-649
>                 URL: https://issues.apache.org/jira/browse/THRIFT-649
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (Java)
>    Affects Versions: 0.2
>         Environment: Centos 5.3
>            Reporter: Anthony Molinaro
>         Attachments: configure.patch, java.patch
>
>
> When creating rpms for centos, I noticed the java docs were being installed 
> in /java instead of /usr/share/java.  This turns out to be a difference 
> between autoconf 2.59 and 2.6x.  Since 2.60 is not available for Centos 5.x, 
> I fixed this by adding a few paths in lib/java/Makefile.am.  This patch works 
> on Centos5.x and Mac OX 10.6.2 (which used autoconf 2.64).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to