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

Sean Yeh commented on IMPALA-5078:
----------------------------------

Hi [~tarmstrong] , 

I am running "make expr-test" at ${IMPALA_HOME} directory but am receiving a 
build error. I received the same error when running "make -j $(nproc) 
expr-test".

I tried resolving the issue on my own, but I am honestly lost. The error I see 
is posted below. 

!Screen Shot 2020-07-10 at 11.16.36 AM.png|width=584,height=311!

I took a look at all the files listed and the most interesting file, 
CMakeError.log, shows that there is an undefined reference with pthread_create.

!Screen Shot 2020-07-10 at 11.27.57 AM.png|width=919,height=961!

I can provide the contents of any other file if needed.

Could the bootstrap_development.sh script set up the environment incorrectly?

 

 

> 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