[
https://issues.apache.org/jira/browse/THRIFT-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563095#comment-13563095
]
Volodymyr Krestiannykov edited comment on THRIFT-1614 at 1/25/13 10:14 PM:
---------------------------------------------------------------------------
Well, this is definitely problem of automake >= 12.
Here is the release info here:
http://lists.gnu.org/archive/html/automake/2012-04/msg00060.html
See "Changes to Yacc and Lex support" section.
Currently not only OS X uses this version of automake, but also Fedora,
OpenSuse, anything else?
The bad thing here that there is not a normal solution, probably we will have
to write all yacc rules directly in
compiler/cpp/src/Makefile (I tried it and it looks like hack)
Any ideas how to do it in a normal way?
Also, I think that, it makes sense to increase the priority of this bug.
was (Author: vkrest):
Well, this is definitely problem of automake >= 12.
Here is the release info here:
http://lists.gnu.org/archive/html/automake/2012-04/msg00060.html
See "Changes to Yacc and Lex support" section.
Currently not only OS X uses this version of automake, but also Fedora,
OpenSuse, anything else?
The bad thing here that there is not a normal solution, probably we will have
to write all yacc rules directly in
compiler/cpp/src/Makefile (I tried it and it looks like hack)
Any ideas how to do it in a normal way?
> Thrift build from svn repo sources fails with automake-1.12
> -----------------------------------------------------------
>
> Key: THRIFT-1614
> URL: https://issues.apache.org/jira/browse/THRIFT-1614
> Project: Thrift
> Issue Type: Bug
> Components: Build Process
> Affects Versions: 0.9
> Environment: Reproduced on OS X 10.7 with homebrew automake-1.12
> Reporter: Andrew Cox
> Assignee: Jake Farrell
>
> The yacc.am included in automake-1.12 creates the file "thrifty.hh" instead
> of "thrifty.h", but the generated file "thriftl.cc" includes "thrifty.h".
> Problem goes away when I downgrade automake to 1.11.5
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
