[
https://issues.apache.org/jira/browse/THRIFT-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791102#action_12791102
]
Anthony Molinaro commented on THRIFT-649:
-----------------------------------------
I can't use the tarball as it does not install erlang and php into their
appropriate directories (patches I've uploaded at THRIFT-646 and THRIFT-647),
it also does not pass make check (patches I've uploaded as THRIFT-650). The
end result I am trying to achieve is RPMs which work with Centos 5.3 (our
production environment) and debs which work with fink on OSX (a common
development environment for our developers writing java in eclipse).
I've been patching things to work this way for sometime, but decided to finally
upload them as others may be interested.
Looking at the macros in the newer autoconf it looks like the only thing they
do is define a type if one doesn't exist on the system, which is not what you
asked for. You said we should fail if those types are not found on the system,
a pattern you used with ptrdiff_t, so I copied that pattern.
I'd really like my various patches for the build system to be included, so I
can stop using svn to build my packages and instead just use the tarball.
> 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.
