[
https://issues.apache.org/jira/browse/METRON-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269956#comment-16269956
]
ASF GitHub Bot commented on METRON-1334:
----------------------------------------
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/849
Instead of trying to explaining my position, I threw together a quick PR to
illustrate my thoughts. Feel free to take another approach. I tested it with
`g++` configured, unconfigured, and not in my PATH on macOS, as well as on a
CentOS 7 with and without gcc installed, and an Ubuntu 14.04 box with an old
version of gcc installed (not C++11 compliant). All worked as expected.
> Add C++11 Compliance Check to 'platform-info.sh'
> ------------------------------------------------
>
> Key: METRON-1334
> URL: https://issues.apache.org/jira/browse/METRON-1334
> Project: Metron
> Issue Type: Sub-task
> Reporter: Nick Allen
> Assignee: Nick Allen
> Fix For: 0.4.1
>
>
> Some of the module dependencies for the Management and Alerts UI must be
> built natively on the host. This requires a C/C++ compiler. In addition, some
> of the dependencies require a C++11 compliant compiler. This is causing
> problems for users who attempt to build Metron on a system with an older
> version of GCC, like CentOS 6.
> Not having a C++11 compliant compiler can cause some non-obvious error
> messages when the build fails. This adds a version check for GCC and also a
> C++11 compliance check. The compiler itself must be on the user's PATH, which
> is what the Node modules also require.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)