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

lqjacklee commented on HADOOP-16123:
------------------------------------

After change the code :  
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/CMakeLists.txt
 . 

#add_executable(test-oom-listener
# main/native/oom-listener/impl/oom_listener.c
# main/native/oom-listener/impl/oom_listener.h
# main/native/oom-listener/test/oom_listener_test_main.cc
#)
#target_link_libraries(test-oom-listener gtest rt)
#output_directory(test-oom-listener test)

 

It can work fine now. I wonder whether the test can be removed ? 

 

 

> Lack of protoc in docker
> ------------------------
>
>                 Key: HADOOP-16123
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16123
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.3.0
>            Reporter: lqjacklee
>            Priority: Minor
>
> During build the source code , do the steps as below : 
>  
> 1, run docker daemon 
> 2, ./start-build-env.sh
> 3, sudo mvn clean install -DskipTests -Pnative 
> the response prompt that : 
> [ERROR] Failed to execute goal 
> org.apache.hadoop:hadoop-maven-plugins:3.3.0-SNAPSHOT:protoc (compile-protoc) 
> on project hadoop-common: org.apache.maven.plugin.MojoExecutionException: 
> 'protoc --version' did not return a version -> 
> [Help 1]
> However , when execute the command : whereis protoc 
> liu@a65d187055f9:~/hadoop$ whereis protoc
> protoc: /opt/protobuf/bin/protoc
>  
> the PATH value : 
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/cmake/bin:/opt/protobuf/bin
>  
> liu@a65d187055f9:~/hadoop$ protoc --version
> libprotoc 2.5.0
>  
>  



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

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

Reply via email to