From simon.urbanek at r-project.org  Thu Dec 29 16:55:36 2016
From: simon.urbanek at r-project.org (Simon Urbanek)
Date: Thu, 29 Dec 2016 10:55:36 -0500
Subject: [Rd] Definition of uintptr_t in Rinterface.h
In-Reply-To: <CA+JCgN0pwwmtPZ+p4Yf2fi1uXb2r-0H1jD+hOj1iWi58EiO-_A@mail.gmail.com>
References: <CA+JCgN0pwwmtPZ+p4Yf2fi1uXb2r-0H1jD+hOj1iWi58EiO-_A@mail.gmail.com>
Message-ID: <3ECD3048-DC04-467B-BD33-787A4E70FE67@r-project.org>

The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now fixed in R-devel - please check if that works for you.

Thanks,
Simon



> On Dec 26, 2016, at 11:25 PM, Laurent Gautier <lgautier at gmail.com> wrote:
> 
> Hi,
> 
> I was recently pointed out that a definition in Rinterface.h can be conflicting
> with a definition in stdint.h:
> 
> /usr/include/R/Rinterface.h has:
> typedef unsigned long uintptr_t;
> 
> /usr/include/stdint.h has:
> typedef unsigned int uintptr_t;
> (when 32bit platform complete definition is:
> 
> #if __WORDSIZE == 64
> # ifndef __intptr_t_defined
> typedef long int                intptr_t;
> #  define __intptr_t_defined
> # endif
> typedef unsigned long int       uintptr_t;
> #else
> # ifndef __intptr_t_defined
> typedef int                     intptr_t;
> #  define __intptr_t_defined
> # endif
> typedef unsigned int            uintptr_t;
> #endif
> 
> )
> 
> Is this expected ? Shouldn't R rely on the definition in stdint.h
> rather than define its own ?
> 
> 
> (report for the issue:
> https://bitbucket.org/rpy2/rpy2/issues/389/failed-to-compile-with-python-360-on-32
> )
> 
> 
> Laurent
> 
> 	[[alternative HTML version deleted]]
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
> 



[Rd] Definition of uintptr_t in Rinterface.h
Simon Urbanek