On 5 July 2018 at 22:19, Göran Broström wrote:
| Thanks Heather and Iñaki: I understand.
|
| I have an old Makevars file in the src directory of the package. I
| guess I can set the flags there?
No, because those get scanned by R CMD check and friends.
For the one you do not want, Heather's
I would suggest not to set the CFLAGS in the package itself - at least not
exclusively. R-admin 6.3.3 (the section I linked before) recommends "to enable
a reasonable amount of diagnostic messaging (“warnings”) when compiling, such
as e.g. -Wall -pedantic for tools from GCC", while R-exts 1.2.1
El jue., 5 jul. 2018 a las 22:23, Göran Broström
() escribió:
>
> Thanks Heather and Iñaki: I understand.
>
> I have an old Makevars file in the src directory of the package. I
> guess I can set the flags there? Now it only contains
>
> # PKG_CFLAGS = -Wall
> # PKG_FFLAGS = -Wall -fbounds-check
>
Thanks Heather and Iñaki: I understand.
I have an old Makevars file in the src directory of the package. I
guess I can set the flags there? Now it only contains
# PKG_CFLAGS = -Wall
# PKG_FFLAGS = -Wall -fbounds-check
PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS)
Göran
On 2018-07-05 17:43
On Thu, Jul 5, 2018, at 3:39 PM, Iñaki Úcar wrote:
> El jue., 5 jul. 2018 a las 16:11, Göran Broström
> () escribió:
> >
> > I am preparing a CRAN release of eha (a trivial change due to a change
> > in the survival package), but when checking the build I get:
> >
> > goran@M6800:~/R$ R CMD chec
El jue., 5 jul. 2018 a las 16:11, Göran Broström
() escribió:
>
> I am preparing a CRAN release of eha (a trivial change due to a change
> in the survival package), but when checking the build I get:
>
> goran@M6800:~/R$ R CMD check --as-cran eha_2.5.2.tar.gz
> ...
> * checking compilation flags us
