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

Wei-Chiu Chuang commented on HDFS-14425:
----------------------------------------

I am on macOS Mojave 10.14.6, but I don't have the issue (branch-3.2 and trunk. 
3.2.0 fails due to YARN-9487)

{noformat}
$ gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
--with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
{noformat}

+1 I think it doesn't hurt to add this fix. At the very least it doesn't break 
the build on my local machine.

> Native build fails on macos due to jlong in hdfs.c
> --------------------------------------------------
>
>                 Key: HDFS-14425
>                 URL: https://issues.apache.org/jira/browse/HDFS-14425
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.2.0
>            Reporter: hunshenshi
>            Assignee: hunshenshi
>            Priority: Major
>              Labels: mac
>
> [WARNING] 
> /Users/xx/tmp/idea/hadoop-3.2.0-src/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfs/hdfs.c:3033:/Users/xx/tmp/idea/hadoop-3.2.0-src/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfs/hdfs.c:3033:4949::
>   warningwarning: : incompatible pointer types passing 'tOffset *' (aka 'long 
> long *') to parameter of type 'jlong *' (aka 'long *') 
> [-Wincompatible-pointer-types]incompatible pointer types passing 'tOffset *' 
> (aka 'long long *') to parameter of type 'jlong *' (aka 'long *') 
> [-Wincompatible-pointer-types]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

Reply via email to