You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2017/12/05 19:35:00 UTC

[jira] [Resolved] (NIFI-4661) The nifi-grpc-bundle is built using externally access binaries which create build portability problems

     [ https://issues.apache.org/jira/browse/NIFI-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Gilman resolved NIFI-4661.
-------------------------------
    Resolution: Fixed

> The nifi-grpc-bundle is built using externally access binaries which create build portability problems
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-4661
>                 URL: https://issues.apache.org/jira/browse/NIFI-4661
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions, Tools and Build
>            Reporter: Joseph Witt
>            Assignee: Joseph Witt
>             Fix For: 1.5.0
>
>
> It has been reported that nifi builds on powerpc environments were failing due to the nifi-grpc-bundle not being able to build in that environment.  It turns out is because the grpc processors use some plugins that access some os specific binaries outside the normal process and for grpc it is not supported yet in the powerpc environment.  No problem so we exclude them for that environment.
> Then, in upgrading to more recent versions of the plugin and grpc libraries the build stopped working in Centos6 environments because the grpc protocol buffers build plugin (protoc) requires GLIBC_2.14 or newer and Centos6 has GLIBC_2.12.
> Given the os and environment specific nature of this component I plan to move inclusion of building this module and inclusion of the nar to requiring explicit profile activation.
> If this PR is merged I will update the website/release build instructions to talk about this specifically so that it is included in the normal releases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)