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 installing bnlearn.
Ok. > However, note that C99 compiler is not required for R so it may > not be available. Since you don't really need any advanced > functionality of C99, it may be a good idea to change it to a more > portable C code. That's what I'm going to do; it's now on the top of my TODO list. >> Is it safe to force gcc to use C99 with either -std=c99 o >> -std=gnu99? >> > > Not in your package as cannot assume gcc in general, but > temporarily for R 2.5.1 on OS X, yes. Thanks for the clarification. -- Marco Scutari Linux Registered User #341807 http://counter.li.org powered by : Debian Sid GNU/Linux (SGI-XFS) Kernel 2.6.21.3 ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel