From: Mike Wray <mike.wray@hp.com>
To: xen-devel@lists.xensource.com
Subject: unstable build broken again
Date: Tue, 24 May 2005 11:57:29 +0100 [thread overview]
Message-ID: <42930899.4020702@hp.com> (raw)
The build is broken in unstable as of change set 1.5121:
>bk pull
>rm -rf dist
>debug=y make world
gcc -Wall -Werror -g3 -D _XOPEN_SOURCE=600 -I ../../tools/python/xen/lowlevel/xc -I
../../tools/libxc -I ../../tools/libxutil -o xcsdump xcsdump.c -L../../tools/libxc
-L../../tools/libxutil \
ctrl_interface.c evtchn.c dump.c -lxc -lxutil
install -d -m0755 -p /home/mjw/repos-bk/xeno-unstable.bk/dist/install//usr/sbin
install -d -m0755 -p /home/mjw/repos-bk/xeno-unstable.bk/dist/install/usr/include
install -m0755 xcs /home/mjw/repos-bk/xeno-unstable.bk/dist/install//usr/sbin
install -m0755 xcsdump /home/mjw/repos-bk/xeno-unstable.bk/dist/install//usr/sbin
install -m0755 xcs_proto.h /home/mjw/repos-bk/xeno-unstable.bk/dist/install/usr/include
make[3]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk/tools/xcs'
make[3]: Entering directory `/home/mjw/repos-bk/xeno-unstable.bk/tools/xcutils'
gcc -m elf_i386 -o xc_restore
gcc: no input files
make[3]: *** [xc_restore] Error 1
make[3]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk/tools/xcutils'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk/tools'
make[1]: *** [tools] Error 2
make[1]: Leaving directory `/home/mjw/repos-bk/xeno-unstable.bk'
make: *** [world] Error 2
Mike
next reply other threads:[~2005-05-24 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 10:57 Mike Wray [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 8:57 unstable build broken again Mike Wray
2005-05-24 9:55 ` Keir Fraser
2005-05-24 12:33 ` David F Barrera
2005-05-24 13:59 ` Mike Wray
2005-05-24 14:27 ` Keir Fraser
2005-05-24 14:33 ` Mike Wray
2005-05-24 15:08 ` Keir Fraser
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=42930899.4020702@hp.com \
--to=mike.wray@hp.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.