Re: [Rd] configure.ac

2017-08-01 Thread Ramón Fallon
Many thanks Peter for your answer. That page was exactly what I was looking for. I suppose I was in too much of a hurry. I didn't developer links on the page R page and quick google didn't give me anything. That's great, thanks! On Tue, Aug 1, 2017 at 4:29 PM, Ramón Fallon wrote: > Hi, > > Jus

Re: [Rd] configure.ac

2017-08-01 Thread Prof Brian Ripley
On 01/08/2017 17:26, peter dalgaard wrote: If you check developer.r-project.org, you'll find links to the scripts that we use for building releases and pre-releases of R. These are usually run on a Mac, but shouldn't require much change for Linux. In particular, notice this lead-in in the prer

Re: [Rd] configure.ac

2017-08-01 Thread peter dalgaard
If you check developer.r-project.org, you'll find links to the scripts that we use for building releases and pre-releases of R. These are usually run on a Mac, but shouldn't require much change for Linux. In particular, notice this lead-in in the prerelease script: rm -rf BUILD-dist mkdir BUILD

[Rd] configure.ac

2017-08-01 Thread Ramón Fallon
Hi, Just a quick mail to mention that I cannot generate a new configure script using autoconf or autoreconf. I had edited the configure.ac and thought ... "oh, that's my fault", but then I tried it on R-patched and R-3.4.1 without touching configure.ac and had the same problems. The "building R p

[Rd] configure.ac clock_gettime (and R_CHECK_FUNCS) incorrect?

2013-03-16 Thread Martin Morgan
When R is configured with CFLAGS=-O2, clock_gettime is included $ nm src/main/libR.a | grep clock_gettime U clock_gettime whereas when configured with -O0 it is not $ nm src/main/libR.a | grep clock_gettime $ Similarly when built as a shared library the linker flags include or