On Thu, Feb 27, 2020 at 11:22:38AM +0100, Roger Pau Monné wrote:
> On Wed, Feb 26, 2020 at 11:33:46AM +, Anthony PERARD wrote:
> > From: Anthony PERARD
> >
> > In a later patch ("xen/build: have the root Makefile generates the
> > CFLAGS), we want to generate the CFLAGS in xen/Makefile, then
On Wed, Mar 04, 2020 at 03:42:36PM +0100, Jan Beulich wrote:
> On 26.02.2020 12:33, Anthony PERARD wrote:
> > --- a/xen/scripts/Kbuild.include
> > +++ b/xen/scripts/Kbuild.include
> > @@ -10,7 +10,7 @@ DEPS_INCLUDE = $(addsuffix .d2, $(basename $(wildcard
> > $(DEPS
> > # as-insn: Check wheth
On 26.02.2020 12:33, Anthony PERARD wrote:
> --- a/xen/scripts/Kbuild.include
> +++ b/xen/scripts/Kbuild.include
> @@ -10,7 +10,7 @@ DEPS_INCLUDE = $(addsuffix .d2, $(basename $(wildcard
> $(DEPS
> # as-insn: Check whether assembler supports an instruction.
> # Usage: cflags-y += $(call as-i
On Wed, Feb 26, 2020 at 11:33:46AM +, Anthony PERARD wrote:
> From: Anthony PERARD
>
> In a later patch ("xen/build: have the root Makefile generates the
> CFLAGS), we want to generate the CFLAGS in xen/Makefile, then export
> it and have Rules.mk use a CFLAGS from the environment variables.
From: Anthony PERARD
In a later patch ("xen/build: have the root Makefile generates the
CFLAGS), we want to generate the CFLAGS in xen/Makefile, then export
it and have Rules.mk use a CFLAGS from the environment variables. That
changes the flavor of the CFLAGS and flags intended for one target
(l
