search for: all_cppflags

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

...RA_LIBS = RANLIB = ranlib SHELL = /bin/sh SHLIBEXT = so SHLIBLD = gcc SHLIBLDFLAGS = -G TAR = tar X_CFLAGS = -I/usr/openwin/include X_LIBS = -L/usr/openwin/lib -R/usr/openwin/lib -lX11 X_PRE_LIBS = -lSM -lICE X_EXTRA_LIBS = -lsocket -lnsl YACC = bison -y ALL_CFLAGS = $(R_XTRA_CFLAGS) $(CFLAGS) ALL_CPPFLAGS = $(R_XTRA_CPPFLAGS) $(CPPFLAGS) $(DEFS) ALL_FFLAGS = $(R_XTRA_FFLAGS) $(FFLAGS) .SUFFIXES: .SUFFIXES: .c .f .d .o .c.d: @echo "making $@ from $<" @$(CC) -M $(ALL_CPPFLAGS) $< > $@ .c.o: $(CC) $(ALL_CPPFLAGS) $(ALL_CFLAGS) -c $< -o $@ .f.o: $(F2C) $(F2CFLAGS) < $&lt...

...iables for dependency lists. TARGET_H = $(TM_H) target.h insn-modes.h MACHMODE_H = machmode.h mode-classes.def insn-modes.h @@ -2048,9 +2051,11 @@ dumpvers: dumpvers.c -version.o: version.c version.h $(DATESTAMP) $(BASEVER) $(DEVPHASE) +.PHONY: version.o +version.o: $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) \ -DBASEVER=$(BASEVER_s) -DDATESTAMP=$(DATESTAMP_s) \ + -DSVNVER=$(SVNVER_s) \ -DDEVPHASE=$(DEVPHASE_s) -c $(srcdir)/version.c $(OUTPUT_OPTION) gtype-desc.o: gtype-desc.c $(CONFIG_H) $(SYSTEM_H) coretypes.h $ (TM_H) \ -------------- next part -------------- An HTML attachment was...

Full_Name: W.B.Kloke Version: 1.9.1 OS: FreeBSD-5.2.1 Submission from: (NULL) (195.253.16.182) Subject line says it. I had problems installing lme4. 1. The dependency on package Matrix was not resolved (I am not sure that this is really a bug; but it is annoying, anyway). 2. Installing Matrix failed with a message saying something like "no rule for %_D.o" after compiling a lot of

...$(TM_H) target.h insn-modes.h > MACHMODE_H = machmode.h mode-classes.def insn-modes.h > @@ -2048,9 +2051,11 @@ > > dumpvers: dumpvers.c > > -version.o: version.c version.h $(DATESTAMP) $(BASEVER) $(DEVPHASE) > +.PHONY: version.o > +version.o: > $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) \ > -DBASEVER=$(BASEVER_s) -DDATESTAMP=$(DATESTAMP_s) \ > + -DSVNVER=$(SVNVER_s) \ > -DDEVPHASE=$(DEVPHASE_s) -c $(srcdir)/version.c $(OUTPUT_OPTION) > > gtype-desc.o: gtype-desc.c $(CONFIG_H) $(SYSTEM_H) coretypes.h $(TM_H) \ > > >

...IG_H FC = g77 FFLAGS = -g -O2 FLIBS = -L/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66 -L/usr/i386-redhat-linux/lib -lg2c -lm FPICFLAGS = -fPIC F2C = F2CFLAGS = SHLIBEXT = so SHLIBLD = gcc SHLIBLDFLAGS = -shared R_XTRA_CFLAGS = -mieee-fp R_XTRA_CPPFLAGS = -I$(R_HOME)/include R_XTRA_FFLAGS = ALL_CPPFLAGS = $(R_XTRA_CPPFLAGS) $(CPPFLAGS) $(DEFS) ALL_CFLAGS = $(R_XTRA_CFLAGS) $(CPICFLAGS) $(CFLAGS) ALL_FFLAGS = $(R_XTRA_FFLAGS) $(FPICFLAGS) $(FFLAGS) .SUFFIXES: .SUFFIXES: .c .f .o .c.o: $(CC) $(ALL_CPPFLAGS) $(ALL_CFLAGS) -c $< -o $@ .f.c: .f.o: $(FC) $(ALL_FFLAGS) -c $< -o $@ $(SHLIB): $...

...n gcc 4.9. The Matrix package also does this awful practice, with CHOLMOD.a COLAMD.a AMD.a SuiteSparse_config.a . One way of fixing R is: diff --git a/src/main/Makefile.in b/src/main/Makefile.in index 908b7ab..ce015b4 100644 --- a/src/main/Makefile.in +++ b/src/main/Makefile.in @@ -86,7 +86,7 @@ ALL_CPPFLAGS = $(ZLIB_CPPFLAGS) $(BZLIB_CPPFLAGS) $(PCRE_CPPFLAGS) \ R_ZLIBS = @BUILD_ZLIB_TRUE@ ../extra/zlib/libz.a R_BZLIBS = @BUILD_BZLIB_TRUE@ ../extra/bzip2/libbz2.a R_PCRE = @BUILD_PCRE_TRUE@ ../extra/pcre/libpcre.a -R_TRE = @BUILD_TRE_TRUE@ ../extra/tre/libtre.a +R_TRE = @BUILD_TRE_TRUE@ `ls ../extra...

...1.4 --- ./Makeconf.in.alpha-patch Thu Aug 19 00:24:49 1999 +++ ./Makeconf.in Sun Sep 12 17:38:27 1999 @@ -56,7 +56,10 @@ .SUFFIXES: .SUFFIXES: .c .f .d .o -@depend_rules_frag@ +# added for alpha (autoconf broken?): +.c.d: + @echo "making $@ from $<" + @$(CC) -M $(ALL_CPPFLAGS) $(ALL_CFLAGS) $< >$@ .c.o: $(CC) $(ALL_CPPFLAGS) $(ALL_CFLAGS) -c $< -o $@ @f77_rules_frag@ 2. aclocal.m4 has many wrong C preprocessor directives "#define"s and "#include"s with "#" not in column 1 (DEC cc wants it there) That means #d...

...S@ R_XTRA_LIBS = @R_XTRA_LIBS@ RANLIB = @RANLIB@ SHELL = /bin/sh SHLIBEXT = @SHLIBEXT@ SHLIBLD = @SHLIBLD@ SHLIBLDFLAGS = @SHLIBLDFLAGS@ TAR = @TAR@ X_CFLAGS = @X_CFLAGS@ X_LIBS = @X_LIBS@ X_PRE_LIBS = @X_PRE_LIBS@ X_EXTRA_LIBS = @X_EXTRA_LIBS@ YACC = @YACC@ ALL_CFLAGS = $(R_XTRA_CFLAGS) $(CFLAGS) ALL_CPPFLAGS = $(R_XTRA_CPPFLAGS) $(CPPFLAGS) $(DEFS) ALL_FFLAGS = $(R_XTRA_FFLAGS) $(FFLAGS) .SUFFIXES: .SUFFIXES: .c .f .d .o @depend_rules_frag@ .c.o: $(CC) $(ALL_CPPFLAGS) $(ALL_CFLAGS) -c $< -o $@ @f77_rules_frag@ prefix = @prefix@ exec_prefix = @exec_prefix@ bindir = @bindir@ datadir = @data...

...;> MACHMODE_H = machmode.h mode-classes.def insn-modes.h >> @@ -2048,9 +2051,11 @@ >> >> dumpvers: dumpvers.c >> >> -version.o: version.c version.h $(DATESTAMP) $(BASEVER) $(DEVPHASE) >> +.PHONY: version.o >> +version.o: >> $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) \ >> -DBASEVER=$(BASEVER_s) -DDATESTAMP=$(DATESTAMP_s) \ >> + -DSVNVER=$(SVNVER_s) \ >> -DDEVPHASE=$(DEVPHASE_s) -c $(srcdir)/version.c $(OUTPUT_OPTION) >> >> gtype-desc.o: gtype-desc.c $(CONFIG_H) $(SYSTEM_H) coretypes.h $ >> (TM_H) \ >> >&...

Dear R users I have started to use gdb for debugging dynloaded C code as described in `Writing R Extensions'. Unfortunately I have run into several problems that I haven't been able to solve: - using `n': how comes that the same line of code appears up to three times (and inbetween the next line and maybe even the second next one?) - using `print' resp. `display': How

...don't really see any cleanup process (eg. making a target clean) - but this may very well be due to my limited understanding of these scripts. Any help/hints on how to proceed? Especially if I want it to be portable? Kasper The full Makevars file: MYCXXFLAGS=-O0 %.o: %.cpp $(CXX) $(ALL_CPPFLAGS) $(ALL_CXXFLAGS) $(MYCXXFLAGS) -c $< -o $@ PKG_CPPFLAGS=\ -imacros R_affx_constants.h\ -Ifusion_sdk/calvin_files/array/src\ -Ifusion_sdk/calvin_files/data/src\ -Ifusion_sdk/calvin_files/exception/src\ -Ifusion_sdk/calvin_files/fusion/src\ -Ifusion_sdk/calvin_files/fusion/src/GCOSAdapter\ -Ifusi...

Dear developers, today I tried to build and install R-devel_2009-01-10 on FreeBSD 8.0-CURRENT (i386) for testing purposes. All went well until compiling the now recommended (integrated) Matrix package. At this point the following break occured: ------------------------------------------------ begin installing recommended package Matrix * Installing *source* package 'Matrix' ... **

I'd like to substitute the Subversion revision number for a string in a package man page every time the package is installed or built. I can assume it is being installed or built from a Subversion working copy. I tried putting a target that depends on FORCE into Makefile or Makevars in the src directory, but it is not being built. What sort of make magic do I need, and where do I put it

...e t, double deg ) { return 2 * pt(t, deg, 0, 0); } We create GetPvalueForT.i, which has /* File : GetPvalueForT.i */ %module GetPvalueForT extern double GetPvalueForT ( double t, double deg ); We use GetPvalueForT: $(srcdir)/GetPvalueForT.c swig -perl5 GetPvalueForT.i gcc $(ALL_CPPFLAGS) $(ALL_CFLAGS) -c GetPvalueForT.c GetPvalueForT_wrap.c -I$(DCDFLIB) -I/usr/local/lib/perl5/5.8.2/sun4-solaris-thread-multi/CORE -Im ld -G GetPvalueForT.o -Im -L. -lRmath -lm GetPvalueForT_wrap.o -o GetPvalueForT in Makefile and we got GetPvalueForT.pm and GetPvalueForT and then we can cal...

Why is it that R places CFLAGS after PKG_CFLAGS and not before when compiling a package (e.g. through R CMD build pkg)? This can be problematic if, for instance, you want to use -O3, but -O2 is in R_HOME/etc/Makeconf. If -O2 (in CFLAGS) appears after -O3 (in PKG_CFLAGS), you are left with what you didn't want: -O2. In R-exts, it says that "Flags which are set in file etc/Makeconf

...ode-classes.def insn-modes.h >>> @@ -2048,9 +2051,11 @@ >>> >>> dumpvers: dumpvers.c >>> >>> -version.o: version.c version.h $(DATESTAMP) $(BASEVER) $(DEVPHASE) >>> +.PHONY: version.o >>> +version.o: >>> $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) \ >>> -DBASEVER=$(BASEVER_s) -DDATESTAMP=$(DATESTAMP_s) \ >>> + -DSVNVER=$(SVNVER_s) \ >>> -DDEVPHASE=$(DEVPHASE_s) -c $(srcdir)/version.c $(OUTPUT_OPTION) >>> >>> gtype-desc.o: gtype-desc.c $(CONFIG_H) $(SYSTEM_H) coretypes.h $ >>>...

Hi We are currently embedding a rather large C++ library in R (BioC), and we want some comments on the portability of how we have approach this. First of, we are not really able to do much about the portability of the basic library, which of course is the main question :) We have an approach which seems to work, I just want a bit of feedback on it.... The way we integrate it into R is

Hi. I am writing some code in C that I would like to link into R. My Makevars file is: PKG_CPPFLAGS=-I/usr/local/include PKG_LIBS=-L/usr/local/lib -lgsl PKG_CFLAGS = -Wall -O0 -g -p -pg The source file is core.c,. and I am compiling using R CMD SHLIB core.c The output is gcc -arch x86_64 -O3 -g -p -std=gnu99 -I/Library/Frameworks/ R.framework/Resources/include

...s.r-project.org/bugzilla3/show_bug.cgi?id=14506 --- src/unix/Makefile.in.orig 2010-12-22 16:58:19.000000000 +0000 +++ src/unix/Makefile.in 2010-12-22 16:54:16.000000000 +0000 @@ -66,7 +66,7 @@ ## we need to build at install time to capture the correct 'rhome' install-Rscript: - $(CC) $(ALL_CPPFLAGS) $(ALL_CFLAGS) -DR_HOME='"$(rhome)"' -o Rscript \ + $(CC) $(ALL_CPPFLAGS) $(ALL_CFLAGS) $(LDFLAGS) -DR_HOME='"$(rhome)"' -o Rscript \ $(srcdir)/Rscript.c @$(MKINSTALLDIRS) "$(DESTDIR)$(Rexecbindir)" @$(INSTALL_PROGRAM) Rscript "$(DESTDIR)$(...