[ 
https://issues.apache.org/jira/browse/IMPALA-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155689#comment-17155689
 ] 

Tim Armstrong commented on IMPALA-5078:
---------------------------------------

The build system is a bit of a beast unfortunately.

I forgot to mention that you need to source the config script before running 
make. That sets a bunch of environment variables that are needed to build 
things. I suspect that might be the problem since it looks like the first error 
is happening because USE_SYSTEM_GCC is undefined. Otherwise maybe the cmake 
files need to be regenerated:

I.e. something like 
{noformat}
  . bin/impala-config.sh
  ./buildall.sh -noclean -cmake_only # If you changed CMake files you need to 
regenerate them like this.
  make expr-test
  make fe # If you changed any of the frontend or java stuff, you might also 
need to rebuild that.
{noformat}

> Break up expr-test.cc
> ---------------------
>
>                 Key: IMPALA-5078
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5078
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Henry Robinson
>            Assignee: Sean Yeh
>            Priority: Minor
>              Labels: newbie, ramp-up
>         Attachments: Screen Shot 2020-06-30 at 12.19.16 PM.png, Screen Shot 
> 2020-07-10 at 11.16.36 AM.png, Screen Shot 2020-07-10 at 11.27.57 AM.png
>
>
> {{expr-test.cc}} clocks in at 7129 lines, which is about enough for my emacs 
> to start slowing down a bit. Let's see if we can refactor it enough to have a 
> couple of test files. Maybe moving all the string instructions into a 
> separate {{expr-string-test.cc}}, and having a common header will be enough 
> to make it a bit more manageable. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to