Tony,
  I hit send before adding the full commands.

  sudo apt-get install libbz2-dev liblzma-dev .

  That would make the command in the helper guide:

   sudo apt-get  cmake gcc g++ libcurl4-openssl-dev uuid-dev uuid
libboost-all-dev libssl-dev doxygen libpython3-dev libbz2-dev liblzma-dev .

   Let me know if that helps and apologies for the omission.

  Thanks,
   Marc

On Wed, Nov 22, 2017 at 5:06 PM, Marc P. <marc.par...@gmail.com> wrote:

> Tony,
>   Try adding libbz2-dev liblzma-dev to your distro if you haven't already.
> I don't think I correctly copied the command for apt-get. My apologies.
>
> On Wed, Nov 22, 2017 at 4:26 PM, Tony Kurc <trk...@gmail.com> wrote:
>
>> I'm having a bit of trouble with running make test - still diagnosing, but
>> it is a segfault. (building on an ubuntu 16.04 docker image).
>>
>> ------------------------------------------------------------
>> -------------------
>> CompressFileBZip
>> ------------------------------------------------------------
>> -------------------
>> /nifi-minifi-cpp-0.3.0-source/libminifi/test/archive-tests/C
>> ompressContentTests.cpp:295
>> ............................................................
>> ...................
>>
>> /nifi-minifi-cpp-0.3.0-source/libminifi/test/archive-tests/C
>> ompressContentTests.cpp:295:
>> FAILED:
>>   {Unknown expression after the reported line}
>> due to a fatal error condition:
>>   SIGSEGV - Segmentation violation signal
>>
>>
>> On Tue, Nov 21, 2017 at 3:07 PM, Marc <phroc...@apache.org> wrote:
>>
>> > Hello Apache NiFi community,
>> >
>> > Please find the associated guidance to help those interested in
>> > validating/verifying the release so they can vote.
>> >
>> > # Download latest KEYS file:
>> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
>> >
>> > # Import keys file:
>> > gpg --import KEYS
>> >
>> > # Pull down nifi-minifi-cpp-0.3.0 source release artifacts for review:
>> >
>> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz
>> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.asc
>> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.md5
>> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.sha1
>> > wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
>> > 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.sha256
>> >
>> > # Verify the signature
>> > gpg --verify nifi-minifi-cpp-0.3.0-source.tar.gz.asc
>> >
>> > # Verify the hashes (md5, sha1, sha256) match the source and what was
>> > provided in the vote email thread
>> > md5sum nifi-minifi-cpp-0.3.0-source.tar.gz
>> > sha1sum nifi-minifi-cpp-0.3.0-source.tar.gz
>> > sha256sum nifi-minifi-cpp-0.3.0-source.tar.gz
>> >
>> > # Untar nifi-minifi-cpp-0.3.0-source.tar.gz
>> > tar xf nifi-minifi-cpp-0.3.0-source.tar.gz
>> >
>> > # Verify the build works
>> >
>> > Be mindful of the pre-requisites required for the C++ version of MiNiFi,
>> > enumerated in the README [1] and the switching to the CMake build system
>> > These can vary from system to system and distribution, an example of the
>> > package listing for a recent Ubuntu release is:
>> >   cmake gcc g++ libcurl4-openssl-dev uuid-dev uuid libboost-all-dev
>> > libssl-dev doxygen libpython3-dev
>> >
>> > Once the required environment is established, a build with testing and
>> > linting can be performed via:
>> >
>> >   cd nifi-minifi-cpp-0.3.0-source
>> >   mkdir build
>> >   cd build
>> >   cmake ..
>> >   make package
>> >   make test
>> >   make linter
>> >
>> > # Verify the contents contain a good README, NOTICE, and LICENSE.
>> >
>> > # Verify the git commit ID is correct
>> >
>> > # Verify the RC was branched off the correct git commit ID
>> >
>> > # Look at the resulting convenience assembly (nifi-minifi-cpp-0.3.0-bin.
>> > tar.gz)
>> > found in your build directory
>> >
>> > # Make sure the README, NOTICE, and LICENSE are present and correct
>> >
>> > # Run the resulting convenience binary and make sure it works as
>> expected
>> >
>> > Be mindful of caveats for this initial release, listed in the README.
>> Since
>> > the convenience binaries include
>> > the scripting extension [2], Python support is needed per our README [1]
>> >
>> > For some additional assistance, a package with configuration files for
>> both
>> > a MiNiFI instance and a NiFi instance available at
>> > https://cwiki.apache.org/
>> > confluence/display/MINIFI/Releasing+MiNiFi#ReleasingMiNiFi-
>> > SampleNiFiandMiNiFiConfigurationtotransmitdatafromMiNiFitoNi
>> > FiviaSitetoSite
>> > The provided sample configuration bundle assumes that NiFi is
>> configured to
>> > listen on port 8081 and has 10001 configured for Site to Site's
>> > nifi.remote.input.socket.port.
>> >
>> > # Send a response to the vote thread indicating a +1, 0, -1 based on
>> your
>> > findings.
>> >
>> > Thank you for your time and effort to validate the release! Please let
>> me
>> > know if you have any questions or need clarification.
>> >
>> > Thanks,
>> > Marc
>> >
>> > [1] https://github.com/apache/nifi-minifi-cpp/blob/
>> > MINIFICPP-304-RC0-0.3.0/
>> > README.md#system-requirements
>> > [2] https://cwiki.apache.org/confluence/pages/viewpage.
>> > action?pageId=74685143
>> >
>>
>
>

Reply via email to