Accidentally sent too soon. The ORC build error I got was probably just an
env issue for me, but here it is in case anyone else had the same issue:

In file included from
ESC[01mESC[K/tmp/arrow-0.15.0.KxYbA/apache-arrow-0.15.0/cpp/build/orc_ep-prefix/src/orc_ep/c++/src/wrap/orc-proto-wrapper.cc:44:0ESC[mESC[K:
ESC[01mESC[K/tmp/arrow-0.15.0.KxYbA/apache-arrow-0.15.0/cpp/build/orc_ep-prefix/src/orc_ep-build/c++/src/orc_proto.pb.cc:970:13:ESC[mESC[K
ESC[01;31mESC[Kerror:
ESC[mESC[K‘ESC[01mESC[Kdynamic_init_dummy_orc_5fproto_2eprotoESC[mESC[K’
defined but not used [-Werror=unused-variable]
 static bool dynamic_init_dummy_orc_5fproto_2eproto = []() {
AddDescriptors_orc_5fproto_2eproto(); return true; }();
ESC[01;32mESC[K             ^ESC[mESC[K
cc1plus: all warnings being treated as errors
make[5]: *** [c++/src/CMakeFiles/orc.dir/wrap/orc-proto-wrapper.cc.o] Error
1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [c++/src/CMakeFiles/orc.dir/all] Error 2
make[3]: *** [all] Error 2

[ 29%] Performing build step for 'orc_ep'
CMake Error at
/tmp/arrow-0.15.0.KxYbA/apache-arrow-0.15.0/cpp/build/orc_ep-prefix/src/orc_ep-stamp/orc_ep-build-RELEASE.cmake:16
(message):
  Command failed: 2

   'make'

  See also


/tmp/arrow-0.15.0.KxYbA/apache-arrow-0.15.0/cpp/build/orc_ep-prefix/src/orc_ep-stamp/orc_ep-build-*.log

CMakeFiles/orc_ep.dir/build.make:111: recipe for target
'orc_ep-prefix/src/orc_ep-stamp/orc_ep-build' failed
make[2]: *** [orc_ep-prefix/src/orc_ep-stamp/orc_ep-build] Error 1
CMakeFiles/Makefile2:1248: recipe for target 'CMakeFiles/orc_ep.dir/all'
failed
make[1]: *** [CMakeFiles/orc_ep.dir/all] Error 2

On Wed, Oct 2, 2019 at 4:12 PM Bryan Cutler <cutl...@gmail.com> wrote:

> +1 (non-binding)
>
> I ran the following on Ubuntu 16.04 4.15.0-64-generic:
> > dev/release/verify-release-candidate.sh binaries 0.15.0 2
> > ARROW_CUDA=OFF \
> TEST_DEFAULT=0 \
> TEST_SOURCE=1 \
> TEST_CPP=1 \
> TEST_PYTHON=1 \
> TEST_JAVA=1 \
> TEST_INTEGRATION=1 \
> dev/release/verify-release-candidate.sh source 0.15.0 2
>
> For source verification I set INTEGRATION_TEST_ARGS="--enable-js=0
> --enable-go=0"
>
> When attempting source verification with defaults, I got the below error
> when building the ORC adapter. It looks like just a warning that is being
> treated as error and seems to be only in
>
> On Wed, Oct 2, 2019 at 7:53 AM Andy Grove <andygrov...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> On Mon, Sep 30, 2019 at 11:57 PM Krisztián Szűcs <
>> szucs.kriszt...@gmail.com>
>> wrote:
>>
>> > Hi,
>> >
>> > I would like to propose the following release candidate (RC2) of Apache
>> > Arrow version 0.15.0. This is a release consiting of 697
>> > resolved JIRA issues[1].
>> >
>> > This release candidate is based on commit:
>> > 40d468e162e88e1761b1e80b3ead060f0be927ee [2]
>> >
>> > The source release rc2 is hosted at [3].
>> > The binary artifacts are hosted at [4][5][6][7].
>> > The changelog is located at [8].
>> >
>> > Please download, verify checksums and signatures, run the unit tests,
>> > and vote on the release. See [9] for how to validate a release
>> candidate.
>> >
>> > The vote will be open for at least 72 hours.
>> >
>> > [ ] +1 Release this as Apache Arrow 0.15.0
>> > [ ] +0
>> > [ ] -1 Do not release this as Apache Arrow 0.15.0 because...
>> >
>> > [1]:
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%200.15.0
>> > [2]:
>> >
>> >
>> https://github.com/apache/arrow/tree/40d468e162e88e1761b1e80b3ead060f0be927ee
>> > [3]:
>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.15.0-rc2
>> > [4]: https://bintray.com/apache/arrow/centos-rc/0.15.0-rc2
>> > [5]: https://bintray.com/apache/arrow/debian-rc/0.15.0-rc2
>> > [6]: https://bintray.com/apache/arrow/python-rc/0.15.0-rc2
>> > [7]: https://bintray.com/apache/arrow/ubuntu-rc/0.15.0-rc2
>> > [8]:
>> >
>> >
>> https://github.com/apache/arrow/blob/40d468e162e88e1761b1e80b3ead060f0be927ee/CHANGELOG.md
>> > [9]:
>> >
>> >
>> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
>> >
>>
>

Reply via email to