(In reply to Atri Bhattacharya from comment #4) > (In reply to Detlef Steuer from comment #3) > > Thx for reporting! Have sent question to upstream. > > Any progress? vtk still fails on Factory/i586 There are two points I got from discussions: 1. The toolchain change to gcc6 is a major point for R and therefore happens only in R-devel. Transistion to gcc6 is not complete right now. Current versions of R (3.3.1) won�t get special treatment for gcc6. (-released/-patched) 2. Concerning this bug the status seems to be (from some discussion) ---------------- AFAICT it's not about R sources not compiling. Rather, SUSE has a failed build of VTK-7.0.0/Filters/StatisticsGnuR/vtkRInterface.cxx which is presumably an interface to R using the embedding API. This #includes Rinterface.h, which contains #if !defined(HAVE_UINTPTR_T) && !defined(uintptr_t) typedef unsigned long uintptr_t; #endif which conflicts with a previous typedef of uintptr_t. The !defined(uintptr_t) bit will not catch it because typedefs are not macros, so HAVE_UINTPTR_T is the only vehicle for telling the compiler about the previous definition. For standalone R, it looks like configure works out the setting of HAVE_UINTPTR_T, but it's not setting it for embedded R uses. Presumably that is for a reason - the embedder might not be using the same compilers, e.g. According to R/doc/manual/R-exts.texi (= the manual "Writing R Extensions"), for embedded R " Note that @code{uintptr_t} is a C99 type for which a substitute is defined in @R{}, so your code needs to define @code{HAVE_UINTPTR_T} appropriately. " Notice "your code". In short, this seems to be is an application error that needs to be fixed downstreams. ----------------------------------------------------------------- The last two lines for me seem relevant for the current problems in VTK. Hope that helps a bit.