You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/02/10 05:05:57 UTC

[jira] Created: (HDFS-1619) Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?

Does libhdfs really need to depend on AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T ?
--------------------------------------------------------------------------------------------------------------

                 Key: HDFS-1619
                 URL: https://issues.apache.org/jira/browse/HDFS-1619
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: Roman Shaposhnik
            Assignee: Konstantin Shvachko


Currently configure.ac uses AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T and AC_TYPE_UINT16_T and thus requires autoconf 2.61 or higher. 
This prevents using it on such platforms as CentOS/RHEL 5.4 and 5.5. Given that those are pretty popular and also given that it is really difficult to find a platform
these days that doesn't natively define  intXX_t types I'm curious as to whether we can simply remove those macros or perhaps fail ONLY if we happen to be on such
a platform. 

Here's a link to GNU autoconf docs for your reference:
    http://www.gnu.org/software/hello/manual/autoconf/Particular-Types.html

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira