search for: fflag

...compilation flags (if any) are needed to ensure that FORTRAN `integer' is equivalent to a C int pointer and FORTRAN `double precision' is equivalent to a C double pointer. This is checked during the configuration process. I'm not an avid FORTRAN user. Can someone tell me what these FFLAGS might be for g77? Thanks. -- Rodney Sparapani Medical College of Wisconsin Sr. Biostatistician Patient Care & Outcomes Research (PCOR) rsparapa at mcw.edu 8701 Watertown Plank Rd., Rm. H2775 (414) 456-8786 (FAX: 6689) PO Box 26509, Milwaukee, WI 53226-...

...y main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... lower case, underscore, extra underscore checking whether fort77 and gcc agree on int and double... configure: WARNING: fort77 and gcc disagree on int and double configure: error: Maybe change CFLAGS or FFLAGS? $ >From `config.log' configure:14869: checking whether fort77 and gcc agree on int and double conftestf.f: cftest: conftestf.o: In function `cftest_': /disks/zebra3/ale/Local/temp/R-1.5.0/conftestf.f:9: undefined reference to `pow_di'collect2: ld returned 1 exit status configu...

...`libRblas.dll.a' is up to date. make[5]: Nothing to be done for `svnonly'. installing C headers make --no-print-directory -C ../extra/intl CFLAGS='-O3 -Wall -pedantic -mtune=core2' -f Makefile.win make --no-print-directory -C ../appl CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../nmath CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../main CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2...

...bin/R The configure script for the successful R installation is the following, CC="cc -xc99 -m64 -xarch=sparcvis2" CPPFLAGS="-I/opt/csw/include" CFLAGS="-xcode=abs64 -xlibmieee -xtarget=ultra3 -xarch=sparcvis2" F77=f95 CXX="CC -m64 -library=stlport4" FC=$F77 FFLAGS="-m64 -xarch=sparcvis2" FCFLAGS=$FFLAGS LDFLAGS="-L/opt/csw/lib/sparcv9 -L/opt/solstudio12.2/prod/lib/v9" export CC CPPFLAGS CFLAGS F77 FFLAGS CXX CXXFLAGS FC FCFLAGS LDFLAGS ./configure --prefix=/apps/sparcv9/R-2.12.0 --with-tcl-config=/opt/csw/lib/tclCo nfig.sh --with-tk-conf...

...an AMD Athlon 64 2800*+* processor running Mandriva 2006_64. After unpacking R-2.2.1.tar.gz I ran ./configure. However, configure stopped prematurely with the message *"configure:27295: WARNING: gfortran and gcc disagree on int and double configure:27297: error: Maybe change CFLAGS or FFLAGS?"* Altough I've looked in both the R_Help archive and R Installation and Administration, I can't find any documentation which says what settings should be for CFLAGS or FFLAGS. I tried to mimic the settings shown on page 31 of R Installation and Administration but that failed to...

...iled R on PC164SX + 21164PC/533 using egcs-1.1.2. All other libraries are Redhat-6.0 default. --- R-0.64.1/configure.in.orig Tue Jun 8 19:05:31 1999 +++ R-0.64.1/configure.in Tue Jun 8 19:06:28 1999 @@ -575,6 +575,7 @@ ;; alpha*linux) CFLAGS="-mieee ${CFLAGS}" + FFLAGS="-mieee ${FFLAGS}" DLLFLAGS=-export-dynamic ;; *linuxaout) To the rpm maintainer: You can simply apply the following patch to the spec file of R-base-0.64.1-5.src.rpm without patching the configure.in patch. I also do not know why CFLAGS need to be -O1 instead of -O2??...

The attached patch should fix the problem with dying imap on "Unrecognized event". The problem is that when we register a handle for IO_ERROR only, we still can get readable/writable event without EV_EOF being set. This case was not handled. -- Vaclav Haisman -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: io-kq.diff URL:

...`libRblas.dll.a' is up to date. make[5]: Nothing to be done for `svnonly'. installing C headers make --no-print-directory -C ../extra/intl CFLAGS='-O3 -Wall -pedantic -mtune=core2' -f Makefile.win make --no-print-directory -C ../appl CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../nmath CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../main CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2...

I've just upgraded to an M3 Mac laptop, and I'm working through getting the right configure settings to build R. The Installation and Administration manual says to have this in config.site: FFLAGS="-g -O2 -mmacos-version-min=11.0" FCFLAGS="-g -O2 -mmacos-version-min=11.0" but those give an error on my system, with it suggesting the FFLAGS and FCFLAGS version option should be -mmacosx-version-min=11.0. I don't know if that's a typo or a change. Besides

...+ # empty mean debug yes + AS_IF([test "x$enable_debug" = "x"], + [enable_debug="yes"]) + + # case of debug + AS_CASE([$enable_debug], + [yes],[ + AC_MSG_RESULT(yes) + CFLAGS="${CFLAGS} -g -O0" + CXXFLAGS="${CXXFLAGS} -g -O0" + FFLAGS="${FFLAGS} -g -O0" + FCFLAGS="${FCFLAGS} -g -O0" + OBJCFLAGS="${OBJCFLAGS} -g -O0" + ], + [info],[ + AC_MSG_RESULT(info) + CFLAGS="${CFLAGS} -g" + CXXFLAGS="${CXXFLAGS} -g" + FFLAGS="${FFLAGS} -g" + FCFLAGS="${FCFLAGS} -g&q...

...`libRblas.dll.a' is up to date. make[5]: Nothing to be done for `svnonly'. installing C headers make --no-print-directory -C ../extra/intl CFLAGS='-O3 -Wall -pedantic -mtune=core2' -f Makefile.win make --no-print-directory -C ../appl CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../nmath CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2' -f Makefile.win make --no-print-directory -C ../main CFLAGS='-O3 -Wall -pedantic -mtune=core2' FFLAGS='-O3 -mtune=core2...

...+ # empty mean debug yes + AS_IF([test "x$enable_debug" = "x"], + [enable_debug="yes"]) + + # case of debug + AS_CASE([$enable_debug], + [yes],[ + AC_MSG_RESULT(yes) + CFLAGS="${CFLAGS} -g -O0" + CXXFLAGS="${CXXFLAGS} -g -O0" + FFLAGS="${FFLAGS} -g -O0" + FCFLAGS="${FCFLAGS} -g -O0" + OBJCFLAGS="${OBJCFLAGS} -g -O0" + ], + [info],[ + AC_MSG_RESULT(info) + CFLAGS="${CFLAGS} -g" + CXXFLAGS="${CXXFLAGS} -g" + FFLAGS="${FFLAGS} -g" + FCFLAGS="${FCFLAGS} -g&q...

...returned 1 exit status + -l:libF90.a -lcl -lisamstub -lm ./configure[2344]: -l:libF90.a: not found. + test -n + echo configure: warning: f90 and gcc disagree on int and double + 1>& 2 configure: warning: f90 and gcc disagree on int and double + echo configure: error: Maybe change CFLAGS or FFLAGS? + 1>& 2 configure: error: Maybe change CFLAGS or FFLAGS? + exit 1 Maybe someone has done this before on HP-UX 10.20 and can offer some help. Thanks, Marcus... -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwie...

...r/lpp/X11/include/X11" LDFLAGS="-L$LIBICONV/lib -L/usr/lib -L/usr/X11R6/lib" CONFIG_SHELL=/usr/bin/bash MAKE=/opt/freeware/bin/make CC="xlc" CXX="xlc++" FC="xlf" F77="xlf" CFLAGS="-qarch=auto -qcache=auto -qtune=auto -O3 -qstrict -ma" FFLAGS="-qarch=auto -qcache=auto -qtune=auto -O3 -qstrict" FCFLAGS="-qarch=auto -qcache=auto -qtune=auto -O3 -qstrict" CXXFLAGS="-qarch=auto -qcache=auto -qtune=auto -O3 -qstrict" export OBJECT_MODE LIBICONV CC CFLAGS CXX CXXFLAGS F77 CPPFLAGS LDFLAGS export CONFIG_SHELL MAK...

Up to now I have got the base R and about half of the packages working on SuSe Linux 5.3 using gcc, g77 and xdevel. The other half, for example: pspline, logspline, KernSmooth, akima, tripack, ppr, principal.curve, cluster, funfit, repeated, event, etc., just won't install. Some of them give warnings at expressions in subroutines (repeated, event, pspline,etc.. I will ask about this in

Up to now I have got the base R and about half of the packages working on SuSe Linux 5.3 using gcc, g77 and xdevel. The other half, for example: pspline, logspline, KernSmooth, akima, tripack, ppr, principal.curve, cluster, funfit, repeated, event, etc., just won't install. Some of them give warnings at expressions in subroutines (repeated, event, pspline,etc.. I will ask about this in

...C="cc -xtarget=native64" export FC="f95 -xtarget=native64" export CXX="CC -xtarget=native64" export CPPFLAGS="-I/usr/sfw/include -I/opt/csw/include" export CFLAGS="-O -xlibmieee" export F77="f95 -xtarget=native64" export CXXFLAGS=-O export FFLAGS="-O4 -xlibmopt -libmil -xvector=lib -fround=nearest" export FCFLAGS=$FFLAGS export LDFLAGS="-L/usr/sfw/lib/sparcv9 -L/opt/csw/lib/sparcv9" export SHLIB_CXXLDFLAGS="-G -lCstd" export BLAS_LIBS=-xlic_lib=sunperf export LIBS="-lmvec" export SHLIB_CFLAGS=-lmvec...

Hi Erik, I've found a middleground for the problem of setting default CFLAGS. I've gone back to setting them if {C,CXX,CPP,LD}FLAGS are unset at the onset of the configure script (i.e., the user hasn't specified anything) and then proceed to set them to the defaults as before. This has been suggested before: https://lists.gnu.org/archive/html/autoconf/2006-04/msg00022.html In

...choice when developing for R, I first got everything done there, using R CMD COMPILE, and R CMD SHLIB. Since g77 complained about the Fortran Codes indentation style, I assumed (after reading g77's manpage) that the Fortran code is given in free-form dialect. Therefore, I added a line PKG_FFLAGS+= -ffree-form to Makevars. Compilation and building went fine and I successfully accessed the routines using dyn.load and .Fortran. My colleague, who wanted this done, runs R under windows. So I learnt how to build a package under windows (readme.packages is a great guide!), and it went all s...

Dear FLAC devs, I would like to get some of our patches merged into master. Most of them deal with adhering to GNU conventions, respectively not overriding flags/variables that are up to the user to set. For instance, honoring $(htmldir) is important, as we have installation paths for the documentation that differ from what is currently coded in the various Makefile.am's. Regards David