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

Jim Brennan commented on HDFS-15971:
------------------------------------

[~gautham], [~elgoiri], [~ebadger] There still seems to be a problem here.   
Our development systems are RHEL7 with GCC 4.8.5.   Until this jira went in, I 
had no problems building native code on that system.  And we don't use docker 
for our builds.    If I revert this change, I can build with no problems.

It looks like HDFS-15740 caused a need for the rhel8 build instructions to be 
updated to change:
{noformat}
CMake 3.1 --> CMake 3.19
GCC 4.8.1 or later --> GCC 9.3.0 or later
{noformat}
The Cmake update seems reasonable, but do these changes really justify updating 
the GCC from 4.8 to 9.3 - that's a pretty significant change.   I don't think 
we usually upgrade dependencies that aggressively.

But my build was still working fine before this jira went in.  Apparently 
previous changes did not require  these upgrades for all platforms.

 [~elgoiri] mentioned fuse dependencies.  Does this change require Linux FUSE?  
 I think that used to be optional.


> Make mkstemp cross platform
> ---------------------------
>
>                 Key: HDFS-15971
>                 URL: https://issues.apache.org/jira/browse/HDFS-15971
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: libhdfs++
>    Affects Versions: 3.4.0
>            Reporter: Gautham Banasandra
>            Assignee: Gautham Banasandra
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>         Attachments: Dockerfile_centos_7, build-log.zip, commit-details.txt
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> mkstemp isn't available in Visual C++. Need to make it cross platform.



--
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