On Thu 04/10/07, Simon Urbanek wrote:
> It was not deliberate. The current R build (R 2.6.0) was modified
> to use -std=gnu99 in the CC section for both architectures instead
> of using CFLAGS, that should solve the problem. A work around for
> older R is to set PKG_CFLAGS=-std=gnu99 when instal
Marco,
On Oct 4, 2007, at 2:05 PM, Marco Scutari wrote:
> I've recently uploaded a package (bnlearn) to CRAN. It builds fine
> on both Linux (32 and 64 bit) and Windows, but fails on MacOSX ix86
> because of C90 vs C99 issues:
>
> http://www.r-project.org/nosvn/R.check/r-patched-macosx-ix86/
On Thu 04/10/07, Prof Brian Ripley wrote:
> You've got more serious problems than that: you cannot assume gcc.
> For example on the SunPro compiler I got
>
[snip]
>
> Note that is in C99 mode, and under Linux.
Hmm. I'm able to reproduce at least some of these errors using
gcc in ansi mode:
[EMAI
You've got more serious problems than that: you cannot assume gcc.
For example on the SunPro compiler I got
cc -I/home/ripley/R/R-devel-SunPro/include
-I/home/ripley/R/R-devel-SunPro/inclu
de -I/usr/local/include-Kpic -xO5 -xc99 -xlibmil -nofstore -c
mutual.infor
mation.c -o mutual.informa
