search for: makeflag

...her than the default ones (which were determined when R was built). You could change the file ``R_HOME'/etc/Makeconf' to reflect your preferences. If you are a Bourne shell user, you can also pass the desired flags to Make (which is used for controlling compilation) via the Make variable `MAKEFLAGS', as in MAKEFLAGS="CFLAGS=-O3" R CMD SHLIB *.c ********************************************************************** Now, something like MAKEFLAGS="CC=gcc-3.0" R CMD SHLIB rc.c -o rc.so works fine, and something like MAKEFLAGS="CC=gcc-3.0 PKG_CFLAGS= -Wall"...

...f, 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 can be overridden by the environment variable MAKEFLAGS (at least for systems using GNU make), as in (Bourne shell syntax)" but this doesn't work if I set either MAKEFLAGS or CFLAGS/CXXFLAGS in my configure.ac script or package Makevars. Does anyone have any ideas on how to reliably override the default CFLAGS/CXXFLAGS given in Makeco...

How can one specify multiple extra flags to R CMD SHLIB? The example in R-exts section 5.5 MAKEFLAGS="CFLAGS=-O3" R CMD SHLIB *.c works for a single flag, but when I try MAKEFLAGS="CFLAGS=-g -O2 -Wall" R CMD SHLIB *.c only the first flag is used and the rest seem to be ignored (version 2.3.1, Mac OS X) -thomas Thomas Lumley Assoc. Professor, Biostatistics tlumley at...

On Sep 19, 2007, at 5:41 PM, Devang Patel wrote: > On Sep 19, 2007, at 4:48 PM, Bill Wendling wrote: > > In llvm-backend.cpp : > > 1086 if (GV->getName() != Name) { > 1087 Function *F = TheModule->getFunction(Name); > 1088 assert(F && F->isDeclaration() && "A function turned > into a global?"); > 1089

.../staff/holzer/CurrentWork/algen/C/temp' make: *** [tst.o] Error 2 Compilation exited abnormally with code 2 at Mon Mar 26 15:10:07 ---------------------------------------- The following alternative ends in an infinite loop: ---------------------------------------- .PHONY: tst.o tst.o: tst.c MAKEFLAGS="CFLAGS=" R CMD COMPILE tst.c ---------------------------------------- ---------------------------------------- cd /u/holzer/CurrentWork/algen/C/temp/ make MAKEFLAGS="CFLAGS=" R CMD COMPILE tst.c make[1]: Entering directory `/users/u1/staff/holzer/CurrentWork/algen/C/temp'...

...h $(EFIINC)/$(EFI_SUBARCH)/%.h: gnuefi ; > .PHONY: gnuefi > gnuefi: > @echo Building gnu-efi for $(EFI_SUBARCH) > - $(topdir)/efi/check-gnu-efi.sh $(EFI_SUBARCH) $(objdir) > + cd $(topdir) && git submodule update --init > + mkdir -p "$(objdir)/gnu-efi" > + MAKEFLAGS= make SRCDIR="$(EFIDIR)" TOPDIR="$(EFIDIR)" \ > + ARCH=$(EFI_SUBARCH) ARFLAGS=rvU -f "$(EFIDIR)/Makefile" + ARCH=$(EFI_SUBARCH) ARFLAGS=$(AROPT) -f "$(EFIDIR)/Makefile" > + MAKEFLAGS= make SRCDIR="$(EFIDIR)" TOPDIR="$(EFIDIR)"...

...k-gnu-efi.sh b/efi/check-gnu-efi.sh index 85305f8..7d99e9a 100755 --- a/efi/check-gnu-efi.sh +++ b/efi/check-gnu-efi.sh @@ -25,7 +25,7 @@ if [ ! \( -f "$objdir/include/efi/$ARCH/efibind.h" -a -f "$objdir/lib/libefi.a" # Syslinux disables built-in implicit rules. export MAKEFLAGS= - ../../efi/build-gnu-efi.sh $ARCH "$objdir" > /dev/null 2>&1 + ../../efi/build-gnu-efi.sh $ARCH "$objdir" if [ $? -ne 0 ]; then printf "Failed to build gnu-efi. " printf "Execute the following command for full details: \n\n" --...

...esult = NEW_NUMERIC(1)); double* ptr=NUMERIC_POINTER(result); double t = *REAL(s); double u = t-floor(t)-0.5; if(u>0) *ptr=-1+4*u; else *ptr=-1-4*u; Rprintf("The value is %f", *ptr); UNPROTECT(1); return result; } }; It is compiled with R CMD SHLIB source.c with flag MAKEFLAGS="CC=g++" If I compile with the default flags I get an error message about an undefined reference to "__gxx_personality_v0". However when I call this code from R with test <- function(t){ .Call("test",t) } dyn.load("./source.dll") test(0) dyn.unload(&q...

...$1 -objdir=$2 - -if [ ! \( -f "$objdir/include/efi/$ARCH/efibind.h" -a -f "$objdir/lib/libefi.a" -a -f "$objdir/lib/libgnuefi.a" \) ]; then - # Build the external project with a clean make environment, as - # Syslinux disables built-in implicit rules. - export MAKEFLAGS= - - ../../efi/build-gnu-efi.sh $ARCH "$objdir" - if [ $? -ne 0 ]; then - printf "Failed to build gnu-efi. " - printf "Execute the following command for full details: \n\n" - printf "build-gnu-efi.sh $ARCH $objdir\n\n" - - exit 1 - fi -else - pri...

...is where the make fails. Any suggestions? *** Error code 1 make: Fatal error: Command failed for target `driver-mysql.o' Current working directory /export/home/nathan/dovecot-1.0.beta3/src/lib-sql *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='lib lib-dict lib-sql lib-ntlm lib-settings lib-charset lib-mail lib -imap lib-index lib-storage lib-auth auth...

...The errors from only editing rules.defs are attached. Index: debian/bin/gencontrol.py =================================================================== --- debian/bin/gencontrol.py (revision 706) +++ debian/bin/gencontrol.py (working copy) @@ -25,6 +25,7 @@ def do_arch_setup(self, vars, makeflags, arch, extra): config_entry = self.config.merge('base', arch) + config_entry_description = self.config.merge('description', arch) for i in ( ('xen-arch', 'XEN_ARCH'), @@ -59,7 +60,11 @@ def do_flavour_setup(self, vars,...

...ution yet. winbuilder's install.out shows data.table's .c files compiled with -O3 on Win32 but -O2 on Win64. The same happens on R-Forge. I gather that some packages don't work with -O3 so the default is -O2. I've tried this in data.table's Makevars (entire contents) : ==== MAKEFLAGS="CFLAGS=-O3" # added CFLAGS=-O3 # added PKG_CFLAGS=-O3 # added all: $(SHLIB) # no change mv $(SHLIB) datatable$(SHLIB_EXT) # no change ==== but -O2 still appears...

From: Sylvain Gault <sylvain.gault at gmail.com> These few patches contain a few improvement about the Makefiles for EFI. Mainly, to rebuild the files when needed, and only when needed. The three shell scripts efi/{check,build,clean}-gnu-efi.sh disappeared and are now integrated as makefile recipes. You'll notice an argument ARFLAGS=rvU to the recursive make calls to gnu-efi. This is

...gt; --- a/ocaml/Makefile.am >> +++ b/ocaml/Makefile.am > [...] >> +# Tell version 3.79 and up of GNU make to not build goals in this >> +# directory in parallel. >> +.NOTPARALLEL: > > ^ This makes building the OCaml subdirectory very slow (I normally > build with MAKEFLAGS=-j9). Was there a reason for adding this? I think I added this because both the mlguestfs.cma and mlguestfs.cmxa targets generate libmlguestfs.a: mlguestfs.cma: libguestfsocaml.a guestfs.cmo $(OCAMLMKLIB) -o mlguestfs \ $(libguestfsocaml_a_OBJECTS) guestfs.cmo \ -L$(top_builddir)/src/.li...

..., including putting all the definitions in an extern "C" block. I still get the same error. Since I don't really understand what the extern "C" is supposed be doing here, I'm being pretty brainless about this. Note of course I'm compiling with a C++ compiler (g++) MAKEFLAGS='CXX=\ g++-3.1 PKG_CXXFLAGS=\ -Wall\ -pedantic\ -Werror\ -Wshadow ' R CMD SHLIB ms.cc -o ms.so Would someone be kind enough to tell me what the correct syntax is? It might also be helpful if someone could point to R code that uses compiled C++ code. Addendum: I looked at the file svm.h i...

...A0=A0 <----------------------------=     - line 7     makedir=0A :=3D $(dir $(call lastword,$(MAKEFILE_LIST)))         MAKEARGS :=3D -C =0A/foo/xen40/xen-4.0.0/linux-2.6-pvops.git     MAKEARGS +=3D O=3D$(if =0A$(patsubst /%,,$(makedir)),$(CURDIR)/)$(patsubst =     %/,%,$(makedir))         MAKEFLAGS=0A +=3D --no-print-directory         .PHONY: all $(MAKECMDGOALS Thanks, CM _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...-disable-fp-elim options being given multiple times. (Sometime they are repeated three or four times). > > Clearly there is some make magic I don't understand here. Does anyone know what is going on? The variables set on the command-line to make are passed along to recursive makes via $(MAKEFLAGS). If you set TARGET_LLCFLAGS on the command-line, every recursive invocation is going to get that same value and will add "-relocation-model=pic -disable-fp-elim" only once. But, if you don't set it on the command-line, make will pick up the value from the environment and add those...

...i fi fi it checks and honours R_MAKEVARS_USER, ~/.R/Makevars, but not src/Makevars I'm not really familiar with the R policy about code comilation, but I consider this a bug but maybee I'm wrong as a side note I solved the problem of overwritting CC for this particular package using MAKEFLAGS="CC=gcc" R CMD INSTALL package best regards Eric

...NEW_NUMERIC(1)); double* ptr=NUMERIC_POINTER(result); double t = *REAL(s); double u = t-floor(t)-0.5; if(u>0) *ptr=-1+4*u; else *ptr=-1-4*u; Rprintf("The value is %f", *ptr); UNPROTECT(1); return result; } }; It is compiled with R CMD SHLIB OrthoFunctions.c with flag MAKEFLAGS="CC=g++" However when I call this code from R with test <- function(t){ .Call("test",t) } dyn.load("./OrthoFunctions.dll") test(0) dyn.unload("./OrthoFunctions.dll") then R crashes. If I compile with the default flags (no extern "C", no _...

Weird issue beyond my make-fu: When running the test-suite, this works fine: make TARGET_LLCFLAGS='-mcpu=cortex-a8 -mattr=+thumb2' TEST=nightly report But this fails: export TARGET_LLCFLAGS='-mcpu=cortex-a8 -mattr=+thumb2' make TEST=nightly report It looks like the following line from Makefile.rules is executed multiple times: TARGET_LLCFLAGS += -relocation-model=pic