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

Íñigo Goiri commented on HDFS-16304:
------------------------------------

Thanks [~sjlee0] for reporting and [~gautham] for the fix.
Merged PR 3625 into trunk; hopefully this will help mitigate the issues.
The thing that concerns me is that we didn't catch this while merging 
HDFS-16300.

> Locate OpenSSL libs for libhdfspp
> ---------------------------------
>
>                 Key: HDFS-16304
>                 URL: https://issues.apache.org/jira/browse/HDFS-16304
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: build, hdfs-client, native
>    Affects Versions: 3.4.0
>         Environment: Linux 5.13.0-1005-gcp #6-Ubuntu SMP Fri Oct 8 15:14:43 
> UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Sangjin Lee
>            Assignee: Gautham Banasandra
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: build-log-debian-10.log, build-log-ubuntu-focal.log, 
> build_failure.txt, git-log-head.log, screenshot-1.png, screenshot-2.png
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The Docker build using {{start-build-env.sh}} is failing since commit 
> 1032724. It can be reproduced with a minimal Ubuntu image and by running 
> {{mvn clean install -Pnative -DskipTests -DskipShade 
> -Dmaven.javadoc.skip=true}} inside the Docker container via 
> {{start-build-env.sh}}.
> The regression was introduced by HDFS-16300 where it removed the line
> {{find_library(OPENSSL_LIBRARY NAMES ${OPENSSL_NAME})}}
> I suspect the CI didn't catch it because of the base image the CI runs with? 
> I'm not 100% certain how real this build issue is, but according to 
> {{BUILDING.txt}}, a base Ubuntu image should be able to build Hadoop using 
> {{start-build-env.sh}}, and that's now broken.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to