From: Ian Campbell <Ian.Campbell@XenSource.com>
To: "You, Yongkang" <yongkang.you@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xensource.com>
Subject: Re: Does latest xen-unstable build failed?
Date: Wed, 26 Sep 2007 17:02:03 +0100 [thread overview]
Message-ID: <1190822523.4381.4.camel@localhost.localdomain> (raw)
In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB02385C1F@pdsmsx413.ccr.corp.intel.com>
On Wed, 2007-09-26 at 23:53 +0800, You, Yongkang wrote:
> Hi Keir,
>
> I got build failure in both IA32 and IA32e platform. The changeset is
> #15961
> The failure log is like:
>
> cp build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz
> /home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961-20070926
> /dist/install/boot/vmlinuz-2.6.18-xen
> cp: cannot stat
> `build-linux-2.6.18-xen_x86_64/arch/x86_64/boot/vmlinuz': No such file
> or directory
> make[2]: *** [build] Error 1
> make[2]: Leaving directory
> `/home/nightly/builds_xen_unstable/xen-3.0-hg-xen_unstable-15961-2007092
> 6'
> make[1]: *** [linux-2.6-xen-install] Error 2
>
I think you need to update your linux-2.6.18-xen.hg subtree. This is not
done automatically to avoid blowing away developer changes but you can
add XEN_LINUX_UPDATE=y to your make command line, or just do the pull
manually.
The actual reason behind the failure is that xen-unstable.hg
15909:202153d094d8 and linux-2.6.18-xen.hg 211:c1f5d027adf7 are mutually
dependant.
Ian.
next prev parent reply other threads:[~2007-09-26 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 15:53 Does latest xen-unstable build failed? You, Yongkang
2007-09-26 16:02 ` Ian Campbell [this message]
2007-09-26 16:09 ` You, Yongkang
2007-09-26 16:14 ` 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=1190822523.4381.4.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=yongkang.you@intel.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.