[
https://issues.apache.org/jira/browse/THRIFT-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664419#action_12664419
]
David Reiss commented on THRIFT-201:
------------------------------------
I have mixed feelings about both. #1 is probably the most foolproof and I
think we should start doing it when we start making releases, but I feel kind
of icky keeping a file in our source tree that is part of an external project.
#2 is lower impact, but it seems like a gross workaround for a bug on the
system. Shouldn't aclocal already be configured to look wherever that system
is installing their m4 files?
> cannot build on debian etch
> ---------------------------
>
> Key: THRIFT-201
> URL: https://issues.apache.org/jira/browse/THRIFT-201
> Project: Thrift
> Issue Type: Bug
> Environment: latest thrift snapshot
> Reporter: Eric Jensen
> Assignee: T Jake Luciani
>
> i don't have any mono installed, but end up with configure dying on:
> checking for zlib >= 1.2.3... no
> ./configure: line 20689: syntax error near unexpected token `MONO,'
> ./configure: line 20689: ` PKG_CHECK_MODULES(MONO, mono >= 1.2.6,
> have_mono=yes, have_mono=no)'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
