Hi *, <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-unstable-src.tgz> from today has 85MB because it containes complete & unclean kernel trees ;-) /nils. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen- > unstable-src.tgz> > > from today has 85MB because it containes complete & unclean > kernel trees ;-)Oops, and I really thought I''d got it right this time :-) I''ll try again... NB: I''m also about to change the name of the install tar ball such that it contains an architecture prefix. Only people who pull it from scripts will likely notice. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Am Freitag, den 01.07.2005, 13:10 +0100 schrieb Ian Pratt:> > <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen- > > unstable-src.tgz> > > > > from today has 85MB because it containes complete & unclean > > kernel trees ;-) > > Oops, and I really thought I''d got it right this time :-) > > I''ll try again... > > NB: I''m also about to change the name of the install tar ball such that > it contains an architecture prefix. Only people who pull it from scripts > will likely notice.If you''re changing names, i''d vote for a bit more consistence. I have managed to make a rpm specfile which builds stable, testing and unstable, but that was a weird hack because of this: branch stable testing unstable tarball 2.0.6 2.0-testing unstable tarball dir 2.0 2.0-testing unstable xm dmesg 2.0.6 (?) 2.0 3.0-devel xen image 2.0.6 2.0-testing 3.0-devel syms file xen-syms-$VER xen-$VER-syms xen-$VER-syms That makes scripting hard. And what about a date string in the testing/unstable snapshot''s names/versions? Btw: "xm dmesg" shows Latest ChangeSet: information unavailable with my builds. Is that a bug? /nils. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi, Seems that the link is not working. It only gives me some 166 bytes file... Regards, Wei On Fri, 1 Jul 2005, Nils Toedtmann wrote:> Hi *, > > <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-unstable-src.tgz> > > from today has 85MB because it containes complete & unclean kernel > trees ;-) > > /nils. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 7/1/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote:> Am Freitag, den 01.07.2005, 13:10 +0100 schrieb Ian Pratt: > > > <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen- > > > unstable-src.tgz> > > > > > > from today has 85MB because it containes complete & unclean > > > kernel trees ;-) > > > > Oops, and I really thought I''d got it right this time :-) > > > > I''ll try again... > > > > NB: I''m also about to change the name of the install tar ball such that > > it contains an architecture prefix. Only people who pull it from scripts > > will likely notice. > > If you''re changing names, i''d vote for a bit more consistence. I have > managed to make a rpm specfile which builds stable, testing and > unstable, but that was a weird hack because of this: > > branch stable testing unstable > tarball 2.0.6 2.0-testing unstable > tarball dir 2.0 2.0-testing unstable > xm dmesg 2.0.6 (?) 2.0 3.0-devel > xen image 2.0.6 2.0-testing 3.0-devel > syms file xen-syms-$VER xen-$VER-syms xen-$VER-syms > > That makes scripting hard. And what about a date string in the > testing/unstable snapshot''s names/versions? > > Btw: "xm dmesg" shows > > Latest ChangeSet: information unavailable >This is not a bug, if you are running stable version. The tree of stable is not BK repo itself, so there is no changeset notation. But if you use bk to pull the unstable or testing version to your machine, then compile it, the "Last ChangeSet" will be shown (of course your machine must install bk) If you are using the code got from Mercurial repo, you must make sure to install "hg" tool on your machine to have those "Latest ChangeSet" ;-) regards, aq _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Am Freitag, den 01.07.2005, 09:49 -0400 schrieb wei huang:> On Fri, 1 Jul 2005, Nils Toedtmann wrote: > > > > <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-unstable-src.tgz> > > > > from today has 85MB because it containes complete & unclean kernel > > trees ;-) > > Seems that the link is not working. > > It only gives me some 166 bytes file...Ian seems to work on the archives. Try again now, i have just fetched a working tarball from today. /nils. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Am Freitag, den 01.07.2005, 23:09 +0900 schrieb aq:> On 7/1/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote: > > > > Btw: "xm dmesg" shows > > > > Latest ChangeSet: information unavailable > > This is not a bug, if you are running stable version. The tree of > stable is not BK repo itself, so there is no changeset notation.I use the testing/unstable snapshot tarballs.> But if you use bk to pull the unstable or testing version to your > machine, then compile it, the "Last ChangeSet" will be shown (of > course your machine must install bk)So there is a piece of bk/hg-metainformation not in the snapshots.> If you are using the code got from Mercurial repo, you must make sure > to install "hg" tool on your machine to have those "Latest ChangeSet" > ;-)Ok. Thanks. /nils. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 7/1/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote:> Am Freitag, den 01.07.2005, 23:09 +0900 schrieb aq: > > On 7/1/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote: > > > > > > Btw: "xm dmesg" shows > > > > > > Latest ChangeSet: information unavailable > > > > This is not a bug, if you are running stable version. The tree of > > stable is not BK repo itself, so there is no changeset notation. > > I use the testing/unstable snapshot tarballs. > > > But if you use bk to pull the unstable or testing version to your > > machine, then compile it, the "Last ChangeSet" will be shown (of > > course your machine must install bk) > > So there is a piece of bk/hg-metainformation not in the snapshots. >indeed. all the SCM metainformation is removed in all the snapshots. so that "Latest Changeset" will not be shown if you dont get the code from repo. lets consider that information is for developers only ;-) regards, aq _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, Jul 01, 2005 at 04:28:49PM +0200, Nils Toedtmann wrote:> Am Freitag, den 01.07.2005, 09:49 -0400 schrieb wei huang: > > On Fri, 1 Jul 2005, Nils Toedtmann wrote: > > > > > > <http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-unstable-src.tgz> > > > > > > from today has 85MB because it containes complete & unclean kernel > > > trees ;-) > > > > Seems that the link is not working. > > > > It only gives me some 166 bytes file... > > Ian seems to work on the archives. Try again now, i have just fetched a > working tarball from today.http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-unstable-install-x86_64.tgz seems still to be broken :-( Building from src is unfortunately not (yet?) successful: make[2]: Entering directory `/home/fh/xen/xen-unstable/tools/check'' ./chk build FAILED check_curl_devel lrwxrwxrwx 1 root root 16 2005-06-28 20:36 /usr/lib/libcurl.so.3 -> libcurl.so.3.0.0 -- Regards Frank _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Building from src is unfortunately not (yet?) successful: > > make[2]: Entering directory `/home/fh/xen/xen-unstable/tools/check'' > ./chk build > FAILED check_curl_devel > > > lrwxrwxrwx 1 root root 16 2005-06-28 20:36 /usr/lib/libcurl.so.3 -> > libcurl.so.3.0.0That means you have the curl package installed. Curl-devel will include the headers, etc, so it''ll probably be a separate package for your distro. You''ll need this to build from source. Cheers, Mark _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-u > nstable-install-x86_64.tgz > seems still to be broken :-(Since the link appeard x86_64 has not been passing the nightly build regression tests, so there''s no binary there for the moment. Hopefully this will get fixed soon... Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Jul 04, 2005 at 10:27:53PM +0100, Mark A. Williamson wrote:> > Building from src is unfortunately not (yet?) successful: > > > > make[2]: Entering directory `/home/fh/xen/xen-unstable/tools/check'' > > ./chk build > > FAILED check_curl_devel > > > > > > lrwxrwxrwx 1 root root 16 2005-06-28 20:36 /usr/lib/libcurl.so.3 -> > > libcurl.so.3.0.0 > > That means you have the curl package installed. Curl-devel will include the > headers, etc, so it''ll probably be a separate package for your distro. > You''ll need this to build from source.uuups. OK, things are ''slightly'' different from FreeBSD. After installing libcurl3-dev things work much better... until the point where ''make dist'' tries to strip a shell-script :-} strip: /home/fh/xen/xen-unstable/dist/install/usr/lib/xen/bin/qemu-dm.debug: File format not recognized install: strip failed root@serv:~# file /home/fh/xen/xen-unstable/dist/install/usr/lib/xen/bin/qemu-dm.debug /home/fh/xen/xen-unstable/dist/install/usr/lib/xen/bin/qemu-dm.debug: Bourne shell script text executable Please fix the Makefile: root@serv:~/xen/xen-unstable/tools/ioemu/target-i386-dm# diff -u Makefile.orig Makefile --- Makefile.orig 2005-07-05 11:25:40.116144312 +0200 +++ Makefile 2005-07-05 11:26:05.338309960 +0200 @@ -385,7 +385,7 @@ if [ ! -d $(INSTALL_DIR) ];then mkdir -p $(INSTALL_DIR);fi if [ ! -d $(DESTDIR)$(configdir) ];then mkdir -p $(DESTDIR)$(configdir);fi install -m 755 -s $(PROGS) "$(INSTALL_DIR)" - install -m 755 -s qemu-dm.debug "$(INSTALL_DIR)" + install -m 755 qemu-dm.debug "$(INSTALL_DIR)" install -m 755 qemu-ifup "$(DESTDIR)$(configdir)" gunzip -c qemu-vgaram-bin.gz >qemu-vgaram-bin install -m 755 qemu-vgaram-bin "$(DESTDIR)$(configdir)" This is Hoary Hedgedog on amd64, JFYI. -- Regards Frank _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel