xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Du Yukun" <yukundu@yeah.net>
To: xen-devel@lists.xen.org
Subject: [stubdom] Makefile configuration failed for user-defined studbom
Date: Thu, 14 Jan 2016 17:08:21 +0800 (CST)	[thread overview]
Message-ID: <1159b47e.19fa.1523f6491c3.Coremail.yukundu@yeah.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]

Hi, everyone!
        I am trying to add my own program as a stubdom. I failed several times with the Makefile. I have add my own party in xen/stubdom/Makefile. It works fine except the mini-os section saying that no rule for target APP_OBJS
I only modified the xen/stubdom/Makefile and configure.ac. Can anyone help me with this problem. Thanks a lot.
    
~~~~~~~~~~~~~~~~~~~~ I added this part into the Makefile in stubdom
 .PHONY: libvmi-stubdom
libvmi-stubdom: mini-os-$(XEN_TARGET_ARCH)-libvmi libxc libvmi
    DEF_CPPFLAGS="$(TARGET_CPPFLAGS)" DEF_CFLAGS="$(TARGET_CFLAGS)" DEF_LDFLAGS="$(TARGET_LDFLAGS)" MINIOS_CONFIG="$(CURDIR)/libvmi/minios.cfg" $(MAKE    ) DESTDIR= -C $(MINI_OS) OBJ_DIR=$(CURDIR)/$< APP_OBJS=$(CURDIR)/libvmi/example/process-list.a

~~~~~~~~~~~~~~~~~~~~

[-- Attachment #1.2: Type: text/html, Size: 1136 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2016-01-14  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  9:08 Du Yukun [this message]
2016-01-14 11:06 ` [stubdom] Makefile configuration failed for user-defined studbom Ian Campbell
2016-01-14 13:27   ` 答复: " Yukun Du
2016-01-14 13:56     ` Ian Campbell
2016-01-14 14:42       ` Du Yukun
2016-01-14 14:58         ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1159b47e.19fa.1523f6491c3.Coremail.yukundu@yeah.net \
    --to=yukundu@yeah.net \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).