search for: safe_fflags

...TRUE The example works perfectly when removing the bounds. However, when bounds are added the snippet returns 'FALSE'. An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store --- > SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse Reverting to the old SAFE_FFLAGS 'solves' the problem. > sessionInfo() R version 3.5.2 (2018-12-20) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Scientific Linux releas...

...bounds. However, when > bounds are added the snippet returns 'FALSE'. > > > > An older R version (3.4.4), compiled using the same gcc-8.2, did not > have the problem. Between the two versions R has changed the flags to > compile Fortran sources: > > > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > > --- > >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > > > >> sessionInfo() > > R version 3.5.2 (2018-12-20) > > P...

...removing the bounds. However, when bounds are added the snippet returns 'FALSE'. > > > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > > --- > >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > > >> sessionInfo() > > R version 3.5.2 (2018-1...

...orks perfectly when removing the bounds. However, when bounds are added the snippet returns 'FALSE'. > > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > --- >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > >> sessionInfo() > R version 3.5.2 (2018-12-20) > Platform: x86_64-pc-linux-gnu (64-bit)...

...works perfectly when removing the bounds. However, when bounds are added the snippet returns 'FALSE'. > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > --- >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > Reverting to the old SAFE_FFLAGS 'solves' the problem. >> sessionInfo() > R version 3.5.2 (2018-12-20) > Platform: x86_64-pc-linux...

...s. However, when bounds are added the snippet returns 'FALSE'. > > > > > An older R version (3.4.4), compiled using the same gcc-8.2, did not have the problem. Between the two versions R has changed the flags to compile Fortran sources: > > > > > < SAFE_FFLAGS = -O2 -fomit-frame-pointer -ffloat-store > > > --- > > >> SAFE_FFLAGS = -O2 -fomit-frame-pointer -msse2 -mfpmath=sse > > > > > Reverting to the old SAFE_FFLAGS 'solves' the problem. > > > > >> sessionInfo() > >...

...pic F77=f95 FFLAGS="-O5 -libmil -nofstore" FPICFLAGS=-Kpic CXX=CC CXXFLAGS="-xO5 -xlibmil -nofstore" CXXPICFLAGS=-Kpic FC=f95 FCFLAGS=$FFLAGS FCPICFLAGS=-Kpic LDFLAGS=-L/opt/sun/sunstudio12/lib/amd64 SHLIB_LDFLAGS=-shared SHLIB_CXXLDFLAGS="-G -lCstd" SHLIB_FCLDFLAGS=-G SAFE_FFLAGS="-O5 -libmil" platform 86_64-unknown-linux-gnu arch x86_64 os linux-gnu system x86_64, linux-gnu...

...ed, otherwise ''. ## FFLAGS= FFLAGS="-g -O2" ## Options for safe compilation under the FORTRAN 77 compiler. ## Use this to specify FFLAGS for the version of the compiler specified ## above, using as accurate a result as possible, e.g. no optimization ## or using -ffloat-store. ## SAFE_FFLAGS= SAFE_FFLAGS="-g" ## The following additional FFLAGS to be used only in the main ## compilation and only in building shared libraries respectively. ## For example, on some systems one needs 'MAIN_FFLAGS=-pg' when ## profiling. ## MAIN_FFLAGS= ## SHLIB_FFLAGS= ## The command to b...

...uot; MAIN_CFLAGS=-g SHLIB_CFLAGS=-g CPPFLAGS="-I. -I/opt/sun/sunstudio12.1/prod/include -I/opt/sun/sunstudio12.1/prod/include/cc" CPPFLAGS+="-I/opt/sun/sunstudio12.1/prod/include/cc/sys -I/usr/local/include" F77=/opt/sun/sunstudio12.1/bin/sunf95 FFLAGS="-g -O -libmil " SAFE_FFLAGS="-g -libmil" CPICFLAGS=-Kpic FPICFLAGS=-Kpic SHLIB_LDFLAGS=-shared LDFLAGS=-L/opt/sun/sunstudio12.1/lib/386 CXX=/opt/sun/sunstudio12.1/bin/sunCC CXXFLAGS="-g -xlibmil -xlibmieee" CXXPICFLAGS=-Kpic SHLIB_CXXLDFLAGS="-G -lCstd" FC=/opt/sun/sunstudio12.1/bin/sunf95 FCFLAG...

Does anybody know why two "-g" flags appear in the call to gcc in R CMD SHLIB Example: gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -fpic *-g* -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 *-g* -c c_file1.c -o c_object1.o Surely it need only be listed once? Alan [[alternative HTML version deleted]]

...pped comments at the start and end of code chunks. It could also fail when \SweaveInput was combined with named chunks. ? The Fortran code used by nls(algorithm = "port") could infinite-loop when compiled with high optimization on a modern version of gcc, and SAFE_FFLAGS is now used to make this less likely. (PR#14427, seen with 32-bit Windows using gcc 4.5.0 used from R 2.12.0.) ? sapply() with default simplify = TRUE and mapply() with default SIMPLIFY = TRUE wrongly simplified language-like results, as, e.g., in mapply(1:2, c(3,7), F...

...pped comments at the start and end of code chunks. It could also fail when \SweaveInput was combined with named chunks. ? The Fortran code used by nls(algorithm = "port") could infinite-loop when compiled with high optimization on a modern version of gcc, and SAFE_FFLAGS is now used to make this less likely. (PR#14427, seen with 32-bit Windows using gcc 4.5.0 used from R 2.12.0.) ? sapply() with default simplify = TRUE and mapply() with default SIMPLIFY = TRUE wrongly simplified language-like results, as, e.g., in mapply(1:2, c(3,7), F...

Dear list, When compiling the R-2.3.0 on FC4 x86_64, I got the following errors: make[3]: Entering directory `/project/scratch3/ligroup/wuming/src/R-2.3.0/src/main' gcc -Wl,--export-dynamic -L/usr/local/lib64 -o R.bin Rmain.o CConverters.o CommandLineArgs.o Rdynload.o Renviron.o RNG.o apply.o arithmetic.o apse.o array.o attrib.o base.o bind.o builtin.o character.o coerce.o colors.o complex.o

(I asked an earlier question on the rpy2 installation to the rpy2 list, the solution there was to edit the setup.py script, but this looks beyond what I can do unless someone tells me exactly what to modify). I have R 2.8.1 on 2 machines running ubuntu 8.04 (packages R-base and R-base-dev, among others, installed using Synaptic) and while the installation of rpy2 went fine on machine1, failed on

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

...rmarkdown from the VignetteBuilder field. INSTALLATION on a UNIX-ALIKE: * Support for a system Java on macOS has been removed - install a fairly recent Oracle Java (see 'R Installation and Administration' SSC.3.2). * configure works harder to set additional flags in SAFE_FFLAGS only where necessary, and to use flags which have little or no effect on performance. In rare circumstances it may be necessary to override the setting of SAFE_FFLAGS. * C99 functions expm1, hypot, log1p and nearbyint are now required. * configure sets a -std flag...

...rmarkdown from the VignetteBuilder field. INSTALLATION on a UNIX-ALIKE: * Support for a system Java on macOS has been removed - install a fairly recent Oracle Java (see 'R Installation and Administration' SSC.3.2). * configure works harder to set additional flags in SAFE_FFLAGS only where necessary, and to use flags which have little or no effect on performance. In rare circumstances it may be necessary to override the setting of SAFE_FFLAGS. * C99 functions expm1, hypot, log1p and nearbyint are now required. * configure sets a -std flag...

...ional build of libRmath.so): this allows a considerable simplification of the Makefiles. o Direct support for f2c has been removed: it can still be used via a script which makes it look like a Fortran compiler. (src/scripts/f77_f2c is an example of such a script.) o There is a new flag SAFE_FFLAGS which is used for the compilation of dlamc.f. It is set by configure for known problem cases (recent g77 and gfortran), but can be overridden by the user. o The standard autoconf macros for large-file support are now used, and these are enabled unless --disable-largefile is specified. Th...

...ional build of libRmath.so): this allows a considerable simplification of the Makefiles. o Direct support for f2c has been removed: it can still be used via a script which makes it look like a Fortran compiler. (src/scripts/f77_f2c is an example of such a script.) o There is a new flag SAFE_FFLAGS which is used for the compilation of dlamc.f. It is set by configure for known problem cases (recent g77 and gfortran), but can be overridden by the user. o The standard autoconf macros for large-file support are now used, and these are enabled unless --disable-largefile is specified. Th...

...env_OBJCFLAGS_value= ac_cv_env_OBJC_set= ac_cv_env_OBJC_value= ac_cv_env_R_BATCHSAVE_set= ac_cv_env_R_BATCHSAVE_value= ac_cv_env_R_BROWSER_set= ac_cv_env_R_BROWSER_value= ac_cv_env_R_PAPERSIZE_set=set ac_cv_env_R_PAPERSIZE_value=letter ac_cv_env_R_PRINTCMD_set= ac_cv_env_R_PRINTCMD_value= ac_cv_env_SAFE_FFLAGS_set= ac_cv_env_SAFE_FFLAGS_value= ac_cv_env_SHLIB_CFLAGS_set= ac_cv_env_SHLIB_CFLAGS_value= ac_cv_env_SHLIB_CXXLDFLAGS_set= ac_cv_env_SHLIB_CXXLDFLAGS_value= ac_cv_env_SHLIB_CXXLD_set= ac_cv_env_SHLIB_CXXLD_value= ac_cv_env_SHLIB_FCD_set= ac_cv_env_SHLIB_FCD_value= ac_cv_env_SHLIB_FCLDFLAGS_set= ac...