Since CPP is being used with CFLAGS, it should be in lock-step with CC, to avoid having to specify both CC and CPP for the build. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2007-03-19/config/StdGNU.mk ==================================================================--- 2007-03-19.orig/config/StdGNU.mk 2007-03-08 09:37:32.000000000 +0100 +++ 2007-03-19/config/StdGNU.mk 2007-03-21 14:33:40.000000000 +0100 @@ -1,7 +1,7 @@ AS = $(CROSS_COMPILE)as LD = $(CROSS_COMPILE)ld CC = $(CROSS_COMPILE)gcc -CPP = $(CROSS_COMPILE)gcc -E +CPP = $(CC) -E AR = $(CROSS_COMPILE)ar RANLIB = $(CROSS_COMPILE)ranlib NM = $(CROSS_COMPILE)nm _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Mar 22, 2007 at 02:09:25PM +0000, Jan Beulich wrote:> Since CPP is being used with CFLAGS, it should be in lock-step with CC, > to avoid having to specify both CC and CPP for the build. > > Signed-off-by: Jan Beulich <jbeulich@novell.com>Applied, thanks Jan. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Possibly Parallel Threads
- [PATCH] x86/numa: fix c/s 20120 (Fix SRAT check for discontig memory)
- [PATCH] x86/ioperm: add new paravirt function update_io_bitmap
- [PATCH] x86/ioperm: add new paravirt function update_io_bitmap
- host cross-compile patch
- [PATCH] x86/ioperm: add new paravirt function update_io_bitmap