Hi, Ian
The error message is this:
```
make[2]: Leaving directory `/usr/src/xen-4.6.0/stubdom/libvmi'
make[1]: Leaving directory `/usr/src/xen-4.6.0/stubdom/libvmi'
DEF_CPPFLAGS="-isystem /usr/src/xen-4.6.0/stubdom/../extras/mini-os/include
-D__MINIOS__ -DHAVE_LIBC -isystem
/usr/src/xen-4.6.0/stubdom/../extras/mini-os/include/posix -isystem
/usr/src/xen-4.6.0/stubdom/../tools/xenstore/include -isystem
/usr/src/xen-4.6.0/stubdom/../extras/mini-os/include/x86 -isystem
/usr/src/xen-4.6.0/stubdom/../extras/mini-os/include/x86/x86_64 -U __linux__ -U
__FreeBSD__ -U __sun__ -nostdinc -isystem
/usr/src/xen-4.6.0/stubdom/../extras/mini-os/include/posix -isystem
/usr/src/xen-4.6.0/stubdom/cross-root-x86_64/x86_64-xen-elf/include -isystem
/usr/lib/gcc/x86_64-redhat-linux/4.8.3/include -isystem
/usr/src/xen-4.6.0/stubdom/lwip-x86_64/src/include -isystem
/usr/src/xen-4.6.0/stubdom/lwip-x86_64/src/include/ipv4 -isystem
/usr/src/xen-4.6.0/stubdom/libvmi/libvmi -I/usr/src/xen-4.6.0/stubdom/include
-I/usr/src/xen-4.6.0/stubdom/../xen/include" DEF_CFLAGS="-mno-red-zone -O1
-fno-omit-frame-pointer -m64 -mno-red-zone -fno-reorder-blocks
-fno-asynchronous-unwind-tables -m64 -g -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable
-Wno-unused-local-typedefs -fno-stack-protector -fno-exceptions"
DEF_LDFLAGS="-nostdlib
-L/usr/src/xen-4.6.0/stubdom/cross-root-x86_64/x86_64-xen-elf/lib"
MINIOS_CONFIG="/usr/src/xen-4.6.0/stubdom/libvmi/minios.cfg" make DESTDIR= -C
/usr/src/xen-4.6.0/stubdom/../extras/mini-os
OBJ_DIR=/usr/src/xen-4.6.0/stubdom/mini-os-x86_64-libvmi
APP_OBJS=/usr/src/xen-4.6.0/stubdom/libvmi/example/process-list.a
make[1]: Entering directory `/usr/src/xen-4.6.0/extras/mini-os'
make[1]: *** No rule to make target
`/usr/src/xen-4.6.0/stubdom/libvmi/example/process-list.a', needed by
`/usr/src/xen-4.6.0/stubdom/mini-os-x86_64-libvmi/mini-os_app.o'. Stop.
make[1]: Leaving directory `/usr/src/xen-4.6.0/extras/mini-os'
make: *** [libvmi-stubdom] Error 2
```
Obviously, It has finished the makefile in /xen/stubdom/libvmi, then it goes
wrong.
I have tried to add related rules, such as `ar process-list.a process-list.o`,
in the Makefile in directory libvmi, but it did not work correctly.
And I didn’t find any related rules in mini-os directory Makefile.
Where should I add the rules to run this correctly? Thanks a lot.
发件人: Ian Campbell
发送时间: 2016年1月14日 19:06
收件人: Du Yukun; xen-devel@lists.xen.org
主题: Re: [Xen-devel] [stubdom] Makefile configuration failed for user-defined
studbom
On Thu, 2016-01-14 at 17:08 +0800, Du Yukun wrote:
> 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
Please post the actual error message.
Please also post in plain text and avoid wrapping (since it is important to
the Makefile syntax). In fact it might be best to post your modifications
(all of them) as a patch to remove any ambiguity.
> 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
> ~~~~~~~~~~~~~~~~~~~~
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
