[GitHub] incubator-hawq pull request #1319: HAWQ-1563. Adapt to run Makefile in /bin/...
Github user larham closed the pull request at: https://github.com/apache/incubator-hawq/pull/1319 ---
[GitHub] incubator-hawq issue #1319: HAWQ-1563. Adapt to run Makefile in /bin/sh
Github user larham commented on the issue: https://github.com/apache/incubator-hawq/pull/1319 Alex pushed, thanks! ---
[jira] [Resolved] (HAWQ-1563) Adapt to run Makefile in /bin/sh
[ https://issues.apache.org/jira/browse/HAWQ-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Denissov resolved HAWQ-1563. -- Resolution: Fixed Fix Version/s: 2.3.0.0-incubating > Adapt to run Makefile in /bin/sh > > > Key: HAWQ-1563 > URL: https://issues.apache.org/jira/browse/HAWQ-1563 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Larry Hamel >Assignee: Alexander Denissov > Fix For: 2.3.0.0-incubating > > > - Since each line of Makefile runs in its own shell, pushd and popd are not > necessary > - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1563) Adapt to run Makefile in /bin/sh
[ https://issues.apache.org/jira/browse/HAWQ-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277803#comment-16277803 ] Alexander Denissov commented on HAWQ-1563: -- Committed: https://github.com/apache/incubator-hawq/commit/9578ab04c80d0d0cc1d93e8a8cde98f9e14b6e7d > Adapt to run Makefile in /bin/sh > > > Key: HAWQ-1563 > URL: https://issues.apache.org/jira/browse/HAWQ-1563 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Larry Hamel >Assignee: Alexander Denissov > > - Since each line of Makefile runs in its own shell, pushd and popd are not > necessary > - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] incubator-hawq issue #1319: HAWQ-1563. Adapt to run Makefile in /bin/sh
Github user denalex commented on the issue: https://github.com/apache/incubator-hawq/pull/1319 Committed: https://github.com/apache/incubator-hawq/commit/9578ab04c80d0d0cc1d93e8a8cde98f9e14b6e7d, closing PR ---
[jira] [Assigned] (HAWQ-1563) Adapt to run Makefile in /bin/sh
[ https://issues.apache.org/jira/browse/HAWQ-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Denissov reassigned HAWQ-1563: Assignee: Alexander Denissov (was: Ed Espino) > Adapt to run Makefile in /bin/sh > > > Key: HAWQ-1563 > URL: https://issues.apache.org/jira/browse/HAWQ-1563 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Larry Hamel >Assignee: Alexander Denissov > > - Since each line of Makefile runs in its own shell, pushd and popd are not > necessary > - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HAWQ-1563) Adapt to run Makefile in /bin/sh
[ https://issues.apache.org/jira/browse/HAWQ-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry Hamel updated HAWQ-1563: -- External issue URL: (was: https://github.com/apache/incubator-hawq/pull/1319) > Adapt to run Makefile in /bin/sh > > > Key: HAWQ-1563 > URL: https://issues.apache.org/jira/browse/HAWQ-1563 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Larry Hamel >Assignee: Ed Espino > > - Since each line of Makefile runs in its own shell, pushd and popd are not > necessary > - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HAWQ-1563) Adapt to run Makefile in /bin/sh
[ https://issues.apache.org/jira/browse/HAWQ-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry Hamel updated HAWQ-1563: -- External issue URL: https://github.com/apache/incubator-hawq/pull/1319 > Adapt to run Makefile in /bin/sh > > > Key: HAWQ-1563 > URL: https://issues.apache.org/jira/browse/HAWQ-1563 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Larry Hamel >Assignee: Ed Espino > > - Since each line of Makefile runs in its own shell, pushd and popd are not > necessary > - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HAWQ-1563) Adapt to run Makefile in /bin/sh
[ https://issues.apache.org/jira/browse/HAWQ-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry Hamel updated HAWQ-1563: -- see PR at https://github.com/apache/incubator-hawq/pull/1319 > Adapt to run Makefile in /bin/sh > > > Key: HAWQ-1563 > URL: https://issues.apache.org/jira/browse/HAWQ-1563 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Larry Hamel >Assignee: Ed Espino > > - Since each line of Makefile runs in its own shell, pushd and popd are not > necessary > - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HAWQ-1563) Adapt to run Makefile in /bin/sh
Larry Hamel created HAWQ-1563: - Summary: Adapt to run Makefile in /bin/sh Key: HAWQ-1563 URL: https://issues.apache.org/jira/browse/HAWQ-1563 Project: Apache HAWQ Issue Type: Bug Components: PXF Reporter: Larry Hamel Assignee: Ed Espino - Since each line of Makefile runs in its own shell, pushd and popd are not necessary - Also, pushd is not supported in /bin/sh, default shell in Ubuntu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] incubator-hawq pull request #1319: Adapt to run Makefile in /bin/sh
GitHub user larham opened a pull request: https://github.com/apache/incubator-hawq/pull/1319 Adapt to run Makefile in /bin/sh - Since each line of Makefile runs in its own shell, pushd and popd are not necessary - Also, pushd is not supported in /bin/sh, default shell in Ubuntu You can merge this pull request into a Git repository by running: $ git pull https://github.com/goutamtadi1/incubator-hawq makefile_bourne_shell Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1319.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1319 commit 6c086af20e83d0cf21a5d5879588cd1ce84c6201 Author: Goutam Tadi Date: 2017-12-04T21:48:03Z Adapt to run Makefile in /bin/sh - Since each line of Makefile runs in its own shell, pushd and popd are not necessary - Also, pushd is not supported in /bin/sh, default shell in Ubuntu Signed-off-by: Larry Hamel ---
[GitHub] incubator-hawq issue #1312: HAWQ-1368 Add option to hawq register to specify...
Github user outofmem0ry commented on the issue: https://github.com/apache/incubator-hawq/pull/1312 Submitted PR for documentation https://github.com/apache/incubator-hawq-docs/pull/135 ---
[GitHub] incubator-hawq issue #1313: HAWQ-1553 Add option to hawq extract to specify ...
Github user outofmem0ry commented on the issue: https://github.com/apache/incubator-hawq/pull/1313 @radarwave Submitted PR for documentation https://github.com/apache/incubator-hawq-docs/pull/134 ---
[jira] [Commented] (HAWQ-1562) Incorrect path to default log directory in documentation
[ https://issues.apache.org/jira/browse/HAWQ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277017#comment-16277017 ] ASF GitHub Bot commented on HAWQ-1562: -- GitHub user outofmem0ry opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/136 HAWQ-1562 Fixed incorrect path to default log directory You can merge this pull request into a Git repository by running: $ git pull https://github.com/outofmem0ry/incubator-hawq-docs document/HAWQ-1562 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq-docs/pull/136.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #136 commit 9c05af6f19c755526679fcd16792d3f272745e85 Author: Shubham Sharma Date: 2017-12-04T16:07:51Z HAWQ-1562 Fixed incorrect path to default log directory > Incorrect path to default log directory in documentation > > > Key: HAWQ-1562 > URL: https://issues.apache.org/jira/browse/HAWQ-1562 > Project: Apache HAWQ > Issue Type: Bug > Components: Documentation >Reporter: Shubham Sharma >Assignee: David Yozie > > In the current documentation six files point to wrong location of default > directories. The default log directory of management utilities is > ~/hawqAdminLogs but the documentation specifies ~/hawq/Adminlogs/ . There > list can be seen > [here|https://github.com/apache/incubator-hawq-docs/search?utf8=%E2%9C%93&q=Adminlogs&type=] > . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HAWQ-1562) Incorrect path to default log directory in documentation
Shubham Sharma created HAWQ-1562: Summary: Incorrect path to default log directory in documentation Key: HAWQ-1562 URL: https://issues.apache.org/jira/browse/HAWQ-1562 Project: Apache HAWQ Issue Type: Bug Components: Documentation Reporter: Shubham Sharma Assignee: David Yozie In the current documentation six files point to wrong location of default directories. The default log directory of management utilities is ~/hawqAdminLogs but the documentation specifies ~/hawq/Adminlogs/ . There list can be seen [here|https://github.com/apache/incubator-hawq-docs/search?utf8=%E2%9C%93&q=Adminlogs&type=] . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1368) normal user who doesn't have home directory may have problem when running hawq register
[ https://issues.apache.org/jira/browse/HAWQ-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276975#comment-16276975 ] ASF GitHub Bot commented on HAWQ-1368: -- GitHub user outofmem0ry opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/135 HAWQ-1368 Add option to hawq register to specify log directory You can merge this pull request into a Git repository by running: $ git pull https://github.com/outofmem0ry/incubator-hawq-docs document/HAWQ-1368 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq-docs/pull/135.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #135 commit 1ac0fb26d0c358876c3a17c678b761132ccc6941 Author: Shubham Sharma Date: 2017-12-04T15:42:15Z HAWQ-1368 Add option to hawq register to specify log directory > normal user who doesn't have home directory may have problem when running > hawq register > --- > > Key: HAWQ-1368 > URL: https://issues.apache.org/jira/browse/HAWQ-1368 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Reporter: Lili Ma >Assignee: Radar Lei > Fix For: backlog > > > HAWQ register stores information in hawqregister_MMDD.log under directory > ~/hawqAdminLogs, and normal user who doesn't have own home directory may > encounter failure when running hawq regsiter. > We can add -l option in order to set the target log directory and file name > of hawq register. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1553) User who doesn't have home directory can not run hawq extract command
[ https://issues.apache.org/jira/browse/HAWQ-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276972#comment-16276972 ] ASF GitHub Bot commented on HAWQ-1553: -- GitHub user outofmem0ry opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/134 HAWQ-1553 Add option to hawq extract to specify log directory You can merge this pull request into a Git repository by running: $ git pull https://github.com/outofmem0ry/incubator-hawq-docs document/HAWQ-1553 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq-docs/pull/134.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #134 commit 7f89466967bfe3d4b3f8f348f83996f8048d5a33 Author: Shubham Sharma Date: 2017-12-04T15:31:33Z HAWQ-1553 Add option to hawq extract to specify log directory > User who doesn't have home directory can not run hawq extract command > - > > Key: HAWQ-1553 > URL: https://issues.apache.org/jira/browse/HAWQ-1553 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Reporter: Shubham Sharma >Assignee: Radar Lei > > HAWQ extract stores information in hawqextract_MMDD.log under directory > ~/hawqAdminLogs, and a user who doesn't have it's own home directory > encounters failure when running hawq extract. > We can add -l option in order to set the target log directory for hawq > extract. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276809#comment-16276809 ] xinzhang commented on HAWQ-1561: {panel:title=My title} This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by HAWQ configure 8.2.15, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure ## - ## ## Platform. ## ## - ## hostname = node3 uname -m = x86_64 uname -r = 2.6.32-642.el6.x86_64 uname -s = Linux uname -v = #1 SMP Tue May 10 17:27:01 UTC 2016 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = x86_64 /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /opt/rh/devtoolset-2/root/usr//bin PATH: /opt/oozie/oozie-4.3.0/bin PATH: /opt/bazel/bazel-0.6.1/output PATH: /opt/scala/scala-bin/bin PATH: /opt/idea/idea-bin/bin PATH: /opt/netdata/netdata-bin/netdata/usr/sbin PATH: /opt/streamcql/stream-cql-bin/bin PATH: /opt/storm/storm-bin/bin PATH: /opt/gradle/gradle-bin/bin PATH: /opt/kafka/kafka-bin/bin PATH: /opt/elasticsearch/elasticsearch-bin/bin PATH: /opt/maven/maven-bin/bin PATH: /opt/nodejs/node-bin/bin PATH: /opt/eagle/eagle-bin/bin PATH: /opt/hive/hive-falcon-bin/bin PATH: /opt/zookeeper/zookeeper-bin/bin PATH: /opt/sbt/sbt/bin PATH: /opt/neo4j/neo4j-community-3.2.1/bin PATH: /usr/java/jdk1.8.0_66/bin PATH: /opt/oozie/oozie-4.3.0 PATH: /root/anaconda2/bin PATH: /opt/rh/devtoolset-2/root/usr//bin PATH: /opt/oozie/oozie-4.3.0/bin PATH: /opt/bazel/bazel-0.6.1/output PATH: /opt/scala/scala-bin/bin PATH: /opt/idea/idea-bin/bin PATH: /opt/netdata/netdata-bin/netdata/usr/sbin PATH: /opt/streamcql/stream-cql-bin/bin PATH: /opt/storm/storm-bin/bin PATH: /opt/gradle/gradle-bin/bin PATH: /opt/kafka/kafka-bin/bin PATH: /opt/elasticsearch/elasticsearch-bin/bin PATH: /opt/maven/maven-bin/bin PATH: /opt/nodejs/node-bin/bin PATH: /opt/eagle/eagle-bin/bin PATH: /opt/hive/hive-falcon-bin/bin PATH: /opt/zookeeper/zookeeper-bin/bin PATH: /opt/sbt/sbt/bin PATH: /opt/neo4j/neo4j-community-3.2.1/bin PATH: /usr/java/jdk1.8.0_66/bin PATH: /usr/lib64/qt-3.3/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /opt/kafka/kafka-eagle/bin PATH: /opt/elasticsearch/logstash-bin/bin PATH: /opt/angel/angel-bin/bin PATH: /root/bin PATH: /opt/kafka/kafka-eagle/bin PATH: /opt/elasticsearch/logstash-bin/bin PATH: /opt/angel/angel-bin/bin ## --- ## ## Core tests. ## ## --- ## configure:2936: checking build system type configure:2950: result: x86_64-unknown-linux-gnu configure:2970: checking host system type configure:2983: result: x86_64-unknown-linux-gnu configure:3005: checking which template to use configure:3088: result: linux configure:3216: checking whether to build with 64-bit integer date/time support configure:3246: result: yes configure:3253: checking whether NLS is wanted configure:3286: result: no configure:3294: checking for default port number configure:3320: result: 5432 configure:3809: checking for gcc configure:3825: found /opt/rh/devtoolset-2/root/usr//bin/gcc configure:3836: result: gcc configure:3867: checking for C compiler version configure:3876: gcc --version >&5 gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15) Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3887: $? = 0 configure:3876: gcc -v >&5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/opt/rh/devtoolset-2/root/usr --mandir=/opt/rh/devtoolset-2/root/usr/share/man --infodir=/opt/rh/devtoolset-2/root/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,fortran,lto --enable-plugin --with-linker-hash-style=gnu --enable-initfini-array --disable-libgcj --with-isl=/dev/shm/home/centos/rpm/BUILD/gcc-4.8.2-20140120/obj-x86_64-redhat-linux/isl-install --with-cloog=/dev/shm/home/centos/rpm/BUILD/gcc-4.8.2-20140120/obj-x86_64-redhat-linux/cloog-install --with-mpc=/dev/shm/home/centos/rpm/BUILD/gcc-4.8.2-20140120/obj-x86_64-redhat-linux/mpc-install --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux Thread model: posix gcc version 4.8.2 20140120 (Red Hat 4.8.2-15) (GCC) configure:3887: $? = 0
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276752#comment-16276752 ] Radar Lei commented on HAWQ-1561: - Hi [~zhangxin0112zx], please provide more error log inside config.log. configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276598#comment-16276598 ] xinzhang edited comment on HAWQ-1561 at 12/4/17 10:38 AM: -- Does your bzip2's version (1.0.5) ? - [root@node3 incubator-hawq]# bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. . [root@node3 incubator-hawq]# rpm -qa |grep bzip2 bzip2-devel-1.0.6-1.bentuos8.0.x86_64 bzip2-libs-1.0.5-7.el6_0.x86_64 bzip2-1.0.5-7.el6_0.x86_64 (I use yum install 1.0.5 with /usr/bin/bzip2 and I install 1.0.6 with source tar in/usr/local/bin/bzip2, I install 1.0.6 to /usr/local) [root@node3 incubator-hawq]# which bzip2 /usr/local/bin/bzip2 [root@node3 incubator-hawq]# whereis bzip2 bzip2: /usr/bin/bzip2 /usr/local/bin/bzip2 /usr/man/man1/bzip2.1 /usr/share/man/man1/bzip2.1.gz - configure log: [root@node3 incubator-hawq]# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking which template to use... linux checking whether to build with 64-bit integer date/time support... yes checking whether NLS is wanted... no checking for default port number... 5432 checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for __get_cpuid... yes checking for __cpuid... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=-msse4.2... yes checking which CRC-32C implementation to use... SSE 4.2 with runtime check checking if gcc supports -Wendif-labels... yes checking if gcc supports -Wformat-security... yes checking if gcc supports -fno-strict-aliasing... yes checking if gcc supports -fwrapv... yes checking if gcc supports -fno-aggressive-loop-optimizations... yes checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E checking whether to build with snmp... no checking whether to build with gphdfs...no checking whether to build with email...no checking allow thread-safe client libraries... yes checking whether to build with Tcl... no checking whether to build Perl modules... no checking whether to build Python modules... no checking whether to build Java modules... no checking whether to build R modules... no checking whether to build pgcrypto modules... no checking whether to build with GSSAPI support... no checking whether to build with Kerberos 5 support... no checking whether to build with PAM support... no checking whether to build with LDAP support... no checking whether to build with Bonjour support... no checking whether to build with OpenSSL support... no checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E configure: using CPPFLAGS= -D_GNU_SOURCE configure: using LDFLAGS= checking for ld used by GCC... /opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld checking if the linker (/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld) is GNU ld... yes checking for ranlib... ranlib checking for strip... strip checking whether it is possible to strip libraries... yes checking for ar... ar checking for tar... /bin/tar checking whether ln -s works... yes checking for gawk... gawk checking for a thread-safe mkdir -p... /bin/mkdir -p checking for bison... /usr/bin/bison configure: using bison (GNU Bison) 3.0.4 checking for flex... /usr/bin/flex configure: using flex 2.5.35 checking for mvn... /opt/maven/maven-bin/bin/mvn configure: using Apache Maven 3.3.9 checking for gperf... /usr/bin/gperf checking for perl... /usr/bin/perl configure: using perl 5.10.1 checking for Perl module JSON... yes checking for python... /root/anaconda2/bin/python checking for main in -lm... yes checking for library containing setproctitle... no checking for library containing dlopen... -ldl checking for library containing socket... none required checking for library containing shl_load... no checking for library containing getopt_long... none required checking for library containing crypt... -lcrypt checking for library containing fdatasync... none required checking for library containing gethostbyname_r... none required checking for library containing shmget... none required checking for library containing readline... -lreadline checking for inflate in -lz... yes checking for clock_gettime in -lrt... yes checking for curl-config... /root/anaconda2/bin/curl-config checki
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276598#comment-16276598 ] xinzhang commented on HAWQ-1561: Does your bzip2's version (1.0.5) ? log: [root@node3 incubator-hawq]# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking which template to use... linux checking whether to build with 64-bit integer date/time support... yes checking whether NLS is wanted... no checking for default port number... 5432 checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for __get_cpuid... yes checking for __cpuid... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=... no checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=-msse4.2... yes checking which CRC-32C implementation to use... SSE 4.2 with runtime check checking if gcc supports -Wendif-labels... yes checking if gcc supports -Wformat-security... yes checking if gcc supports -fno-strict-aliasing... yes checking if gcc supports -fwrapv... yes checking if gcc supports -fno-aggressive-loop-optimizations... yes checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E checking whether to build with snmp... no checking whether to build with gphdfs...no checking whether to build with email...no checking allow thread-safe client libraries... yes checking whether to build with Tcl... no checking whether to build Perl modules... no checking whether to build Python modules... no checking whether to build Java modules... no checking whether to build R modules... no checking whether to build pgcrypto modules... no checking whether to build with GSSAPI support... no checking whether to build with Kerberos 5 support... no checking whether to build with PAM support... no checking whether to build with LDAP support... no checking whether to build with Bonjour support... no checking whether to build with OpenSSL support... no checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E configure: using CPPFLAGS= -D_GNU_SOURCE configure: using LDFLAGS= checking for ld used by GCC... /opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld checking if the linker (/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld) is GNU ld... yes checking for ranlib... ranlib checking for strip... strip checking whether it is possible to strip libraries... yes checking for ar... ar checking for tar... /bin/tar checking whether ln -s works... yes checking for gawk... gawk checking for a thread-safe mkdir -p... /bin/mkdir -p checking for bison... /usr/bin/bison configure: using bison (GNU Bison) 3.0.4 checking for flex... /usr/bin/flex configure: using flex 2.5.35 checking for mvn... /opt/maven/maven-bin/bin/mvn configure: using Apache Maven 3.3.9 checking for gperf... /usr/bin/gperf checking for perl... /usr/bin/perl configure: using perl 5.10.1 checking for Perl module JSON... yes checking for python... /root/anaconda2/bin/python checking for main in -lm... yes checking for library containing setproctitle... no checking for library containing dlopen... -ldl checking for library containing socket... none required checking for library containing shl_load... no checking for library containing getopt_long... none required checking for library containing crypt... -lcrypt checking for library containing fdatasync... none required checking for library containing gethostbyname_r... none required checking for library containing shmget... none required checking for library containing readline... -lreadline checking for inflate in -lz... yes checking for clock_gettime in -lrt... yes checking for curl-config... /root/anaconda2/bin/curl-config checking for curl >= 7.0.0... yes checking CURL_CFLAGS... -I/root/anaconda2/include checking CURL_LIBS... -L/root/anaconda2/lib -lcurl checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking bzlib.h usability... yes checking bzlib.h presence... yes checking for bzlib.h... yes checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. [root@node3
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276568#comment-16276568 ] Paul Guo commented on HAWQ-1561: I just tried. I could run configure with this version. My bzip2 and bzip2-devel was installed via "yum install". If you 1.0.5 does not work you could provide the error information. > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276546#comment-16276546 ] xinzhang commented on HAWQ-1561: Ye. I noticed it . Centos6.X use bzip2-devel (1.0.5) I could not find any rpm(1.0.6) with google. https://rpmfind.net/linux/rpm2html/search.php?query=bzip2-devel I tried use 1.0.5 , it is incorrect. Could u apply any relate links? > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276543#comment-16276543 ] Paul Guo commented on HAWQ-1561: You need to install bzip2-devel Admittedly, configure error message should be explicit. > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HAWQ-1561) build faild on centos 6.8 bzip2
xinzhang created HAWQ-1561: -- Summary: build faild on centos 6.8 bzip2 Key: HAWQ-1561 URL: https://issues.apache.org/jira/browse/HAWQ-1561 Project: Apache HAWQ Issue Type: Bug Components: Build Reporter: xinzhang Assignee: Radar Lei Hi. My env is CentOS release 6.8 . env: # bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. fail log: ... checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. q: CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest pros. What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HAWQ-1561) build faild on centos 6.8 bzip2
[ https://issues.apache.org/jira/browse/HAWQ-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xinzhang updated HAWQ-1561: --- Description: Hi. My env is CentOS release 6.8 . env: # bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. fail log: ... checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. q: CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest pros. What should I to do ? bzip2 1.0.6 had installed . was: Hi. My env is CentOS release 6.8 . env: # bzip2 --version bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. fail log: ... checking for library containing BZ2_bzDecompress... no configure: error: library 'bzip2' is required. 'bzip2' is used for table compression. Check config.log for details. It is possible the compiler isn't looking in the proper directory. q: CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest pros. What should I to do ? bzip2 1.0.6 had installed . > build faild on centos 6.8 bzip2 > --- > > Key: HAWQ-1561 > URL: https://issues.apache.org/jira/browse/HAWQ-1561 > Project: Apache HAWQ > Issue Type: Bug > Components: Build >Reporter: xinzhang >Assignee: Radar Lei > > Hi. My env is CentOS release 6.8 . > env: > # bzip2 --version > bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010. > fail log: >... > checking for library containing BZ2_bzDecompress... no > configure: error: library 'bzip2' is required. > 'bzip2' is used for table compression. Check config.log for details. > It is possible the compiler isn't looking in the proper directory. > q: > CENTOS 6.X use bzip1.0.5 as default . The dependence libs are the biggest > pros. >What should I to do ? bzip2 1.0.6 had installed . -- This message was sent by Atlassian JIRA (v6.4.14#64029)