[jira] [Updated] (HAWQ-914) Improve user experience of HAWQ's build infrastructure
[
https://issues.apache.org/jira/browse/HAWQ-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ed Espino updated HAWQ-914:
---
Labels: (was: ToBeClosed)
> Improve user experience of HAWQ's build infrastructure
> --
>
> Key: HAWQ-914
> URL: https://issues.apache.org/jira/browse/HAWQ-914
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Build
>Affects Versions: 2.0.0.0-incubating
>Reporter: Roman Shaposhnik
>Assignee: Paul Guo
> Fix For: 2.1.0.0-incubating
>
>
> This is likely to end up being an umbrella JIRA so feel free to fork off
> sub-tasks whenever it makes sense.
> As an end-user of HAWQ's build system, I'd like to see the default of the
> build system (running configure/etc. with no arguments) to be:
> # treating optional missing dependencies with a WARNING similar to what
> PostrgreSQL configure does in the following example:
> {noformat}
> checking for bison... no
> configure: WARNING:
> *** Without Bison you will not be able to build PostgreSQL from CVS nor
> *** change any of the parser definition files. You can obtain Bison from
> *** a GNU mirror site. (If you are using the official distribution of
> *** PostgreSQL then you do not need to worry about this, because the Bison
> *** output is pre-generated.) To use a different yacc program (possible,
> *** but not recommended), set the environment variable YACC before running
> *** 'configure'.
> {noformat}
> # treating all the missing suggested dependencies by failing the build and
> suggesting how to point at binary copies of these missing dependencies
> similar to what PostrgreSQL configure does in the following example:
> {noformat}
> checking for -ledit... no
> configure: error: readline library not found
> If you have readline already installed, see config.log for details on the
> failure. It is possible the compiler isn't looking in the proper directory.
> Use --without-readline to disable readline support.
> {noformat}
> # treating the core dependencies same as suggested dependencies, but
> obviously about the option of continuing the build without them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HAWQ-914) Improve user experience of HAWQ's build infrastructure
[
https://issues.apache.org/jira/browse/HAWQ-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goden Yao updated HAWQ-914:
---
Fix Version/s: 2.0.1.0-incubating
> Improve user experience of HAWQ's build infrastructure
> --
>
> Key: HAWQ-914
> URL: https://issues.apache.org/jira/browse/HAWQ-914
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Build
>Affects Versions: 2.0.0.0-incubating
>Reporter: Roman Shaposhnik
>Assignee: Paul Guo
> Fix For: 2.0.1.0-incubating
>
>
> This is likely to end up being an umbrella JIRA so feel free to fork off
> sub-tasks whenever it makes sense.
> As an end-user of HAWQ's build system, I'd like to see the default of the
> build system (running configure/etc. with no arguments) to be:
> # treating optional missing dependencies with a WARNING similar to what
> PostrgreSQL configure does in the following example:
> {noformat}
> checking for bison... no
> configure: WARNING:
> *** Without Bison you will not be able to build PostgreSQL from CVS nor
> *** change any of the parser definition files. You can obtain Bison from
> *** a GNU mirror site. (If you are using the official distribution of
> *** PostgreSQL then you do not need to worry about this, because the Bison
> *** output is pre-generated.) To use a different yacc program (possible,
> *** but not recommended), set the environment variable YACC before running
> *** 'configure'.
> {noformat}
> # treating all the missing suggested dependencies by failing the build and
> suggesting how to point at binary copies of these missing dependencies
> similar to what PostrgreSQL configure does in the following example:
> {noformat}
> checking for -ledit... no
> configure: error: readline library not found
> If you have readline already installed, see config.log for details on the
> failure. It is possible the compiler isn't looking in the proper directory.
> Use --without-readline to disable readline support.
> {noformat}
> # treating the core dependencies same as suggested dependencies, but
> obviously about the option of continuing the build without them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HAWQ-914) Improve user experience of HAWQ's build infrastructure
[
https://issues.apache.org/jira/browse/HAWQ-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Chang updated HAWQ-914:
---
Assignee: Paul Guo (was: Lei Chang)
> Improve user experience of HAWQ's build infrastructure
> --
>
> Key: HAWQ-914
> URL: https://issues.apache.org/jira/browse/HAWQ-914
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Build
>Affects Versions: 2.0.0.0-incubating
>Reporter: Roman Shaposhnik
>Assignee: Paul Guo
>
> This is likely to end up being an umbrella JIRA so feel free to fork off
> sub-tasks whenever it makes sense.
> As an end-user of HAWQ's build system, I'd like to see the default of the
> build system (running configure/etc. with no arguments) to be:
> # treating optional missing dependencies with a WARNING similar to what
> PostrgreSQL configure does in the following example:
> {noformat}
> checking for bison... no
> configure: WARNING:
> *** Without Bison you will not be able to build PostgreSQL from CVS nor
> *** change any of the parser definition files. You can obtain Bison from
> *** a GNU mirror site. (If you are using the official distribution of
> *** PostgreSQL then you do not need to worry about this, because the Bison
> *** output is pre-generated.) To use a different yacc program (possible,
> *** but not recommended), set the environment variable YACC before running
> *** 'configure'.
> {noformat}
> # treating all the missing suggested dependencies by failing the build and
> suggesting how to point at binary copies of these missing dependencies
> similar to what PostrgreSQL configure does in the following example:
> {noformat}
> checking for -ledit... no
> configure: error: readline library not found
> If you have readline already installed, see config.log for details on the
> failure. It is possible the compiler isn't looking in the proper directory.
> Use --without-readline to disable readline support.
> {noformat}
> # treating the core dependencies same as suggested dependencies, but
> obviously about the option of continuing the build without them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HAWQ-914) Improve user experience of HAWQ's build infrastructure
[
https://issues.apache.org/jira/browse/HAWQ-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated HAWQ-914:
--
Affects Version/s: 2.0.0.0-incubating
> Improve user experience of HAWQ's build infrastructure
> --
>
> Key: HAWQ-914
> URL: https://issues.apache.org/jira/browse/HAWQ-914
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Build
>Affects Versions: 2.0.0.0-incubating
>Reporter: Roman Shaposhnik
>Assignee: Lei Chang
>
> This is likely to end up being an umbrella JIRA so feel free to fork off
> sub-tasks whenever it makes sense.
> As an end-user of HAWQ's build system, I'd like to see the default of the
> build system (running configure/etc. with no arguments) to be:
> # treating optional missing dependencies with a WARNING similar to what
> PostrgreSQL configure does in the following example:
> {noformat}
> checking for bison... no
> configure: WARNING:
> *** Without Bison you will not be able to build PostgreSQL from CVS nor
> *** change any of the parser definition files. You can obtain Bison from
> *** a GNU mirror site. (If you are using the official distribution of
> *** PostgreSQL then you do not need to worry about this, because the Bison
> *** output is pre-generated.) To use a different yacc program (possible,
> *** but not recommended), set the environment variable YACC before running
> *** 'configure'.
> {noformat}
> # treating all the missing suggested dependencies by failing the build and
> suggesting how to point at binary copies of these missing dependencies
> similar to what PostrgreSQL configure does in the following example:
> {noformat}
> checking for -ledit... no
> configure: error: readline library not found
> If you have readline already installed, see config.log for details on the
> failure. It is possible the compiler isn't looking in the proper directory.
> Use --without-readline to disable readline support.
> {noformat}
> # treating the core dependencies same as suggested dependencies, but
> obviously about the option of continuing the build without them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
