[
https://issues.apache.org/jira/browse/MINIFI-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676967#comment-15676967
]
Aldrin Piri commented on MINIFI-118:
------------------------------------
I understand this is an inconvenience but am also of the opinion that it is not
an unfair requirement given the period of time since its release.
To get a more informed decision of where the issues arise, do you have a
listing of the problem areas?
Off the top of my head, while supported now, I believe the latest (and current
release, 0.5.3) of yaml-cpp that we are using is the last before C++11 is
required.
Overall, if it's a small gap, maybe we can adjust, but also don't want to
preclude us from using the latest libraries nor get in a position where we have
to manage this compatibility for things upon which we depend. I could also see
where we have varying levels of compatibility wherein some of our core
libraries/framework items are maybe using pre-C++11 type work and our higher
level more outward facing components run off more current versions.
Let me know your thoughts.
> MiNiFi does not compile under Centos 6 standard tooling
> -------------------------------------------------------
>
> Key: MINIFI-118
> URL: https://issues.apache.org/jira/browse/MINIFI-118
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Affects Versions: 0.0.1
> Reporter: Andre
>
> Reliance on C++11 is a big issue as default (i.e. no SCL) tooling on RHEL6
> does not support C++11 fully.
> Using Software collections to deploy later version of the toolchain produce
> valid binary
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
