Juergen Gross writes ("Re: [Xen-devel] [PATCH 1/4] interface: avoid redefinition of __XEN_INTERFACE_VERSION__"): > Hmm, maybe this is the problem: the value from the command line is > (textually) __XEN_LATEST_INTERFACE_VERSION__ while the value from the > #define is the _value_ of __XEN_LATEST_INTERFACE_VERSION__ due to the > pre-processor having replaced it already. > > In case this makes sense, my suggestion seems to be appropriate, no?
Maybe. Another possibly would be to contrive to #define __XEN_INTERFACE_VERSION__ before __XEN_LATEST_INTERFACE_VERSION__. Then the second substitution would occur later. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel