>>> On 20.02.18 at 11:06, <roger....@citrix.com> wrote: > On Tue, Feb 20, 2018 at 02:04:24AM -0700, Jan Beulich wrote: >> >>> On 20.02.18 at 09:23, <roger....@citrix.com> wrote: >> > --- a/tools/firmware/xen-dir/Makefile >> > +++ b/tools/firmware/xen-dir/Makefile >> > @@ -48,10 +48,10 @@ shim-%config: $(D) FORCE >> > KCONFIG_CONFIG=$(CURDIR)/shim.config >> > >> > xen-shim: $(D) shim-olddefconfig >> > - $(MAKE) -C $(D)/xen install-shim \ >> > + $(MAKE) -C $(D)/xen build \ >> >> install-xen ? > > If the install target is used it's more complicated to fetch the > symbols file afterwards, because it's going to contain the Xen version > in the name. The symbols file when using the install target is at: > > $(DESTDIR)$(DEBUG_DIR)/xen-syms-$(XEN_FULLVERSION) > > And obtaining XEN_FULLVERSION from the xen-shim build makefile is not > trivial.
Fair enough. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel