[jira] [Resolved] (IMPALA-8475) buildall.sh fails with undefined CMAKE_BUILD_TYPE_LIST on Centos

["Joe McDonnell (JIRA)" <ji...@apache.org>]

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

Joe McDonnell resolved IMPALA-8475.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> buildall.sh fails with undefined CMAKE_BUILD_TYPE_LIST on Centos
> ----------------------------------------------------------------
>
>                 Key: IMPALA-8475
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8475
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 3.3.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Blocker
>              Labels: broken-build
>             Fix For: Impala 3.3.0
>
>
> A recent change added a bash array to keep track of which build types had been specified to buildall.sh. On Ubuntu, everything seems to work. On Centos, this is producing an error:
> {noformat}
> 15:23:15 /data/jenkins/workspace/impala-asf-master-core/repos/Impala/buildall.sh: line 316: CMAKE_BUILD_TYPE_LIST[0]: unbound variable{noformat}
> Given that this is on a debug build, that should mean that the CMAKE_BUILD_TYPE_LIST is empty. The current theory is that Ubuntu and Centos treat [[ -v VARNAME ]] differently, so in the following code, we are entering the block even with an empty list:
> {code:java}
> if [[ -v CMAKE_BUILD_TYPE_LIST ]]; then
>   if [[ ${#CMAKE_BUILD_TYPE_LIST[@]} -gt 1 ]]; then
>     echo "ERROR: more than one CMake build type defined: ${CMAKE_BUILD_TYPE_LIST[@]}"
>     exit 1
>   fi
>   CMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE_LIST[0]}
> fi
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)