From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Schinker <ba1020@homie.homelinux.net>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.8] ipxe: update to newer commit
Date: Thu, 13 Oct 2016 10:29:38 +0100 [thread overview]
Message-ID: <20161013092938.GB3687@citrix.com> (raw)
In-Reply-To: <1988374135.1390.1476349846215.JavaMail.zimbra@homie.homelinux.net>
On Thu, Oct 13, 2016 at 10:10:46AM +0100, Juergen Schinker wrote:
> Right and still no solution
>
> there is no xz-dev or libxz-dev; I installed everything which just looks remote like xz or lzma
>
On Debian it is called liblzma-dev. Not sure what distro you use.
> building is no problem as I build with
>
> ./configure --enable-githttp --enable-systemd --disable-rombios --disable-qemu-traditional --disable-stubdom --disable-docs
>
>
And you sorta worked around the lzma requirement by disabling rombios.
This issue you encountered is a different issue from Boris'.
Wei.
> I'm thinking of building a special VM with only stable Debian and old gcc and old everything - Pepperidge Farm remembers
>
> and build there
>
> ----- On 13 Oct, 2016, at 09:04, Wei Liu wei.liu2@citrix.com wrote:
>
> > I don't think it breaks building Xen -- you just can't decompress xz
> > format file, right? Otherwise Juergen would not have been able to build
> > Xen.
> >
> > Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-13 9:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 12:50 [PATCH for-4.8] ipxe: update to newer commit Wei Liu
2016-10-10 15:34 ` Ian Jackson
2016-10-10 15:44 ` Wei Liu
2016-10-10 15:51 ` Ian Jackson
2016-10-10 16:33 ` Wei Liu
2016-10-10 17:38 ` Boris Ostrovsky
2016-10-11 9:40 ` Wei Liu
2016-10-11 9:52 ` Ian Jackson
2016-10-11 12:52 ` Boris Ostrovsky
2016-10-11 13:32 ` Ian Jackson
2016-10-11 14:27 ` Boris Ostrovsky
2016-10-11 14:54 ` Ian Jackson
2016-10-11 17:11 ` Boris Ostrovsky
2016-10-12 11:00 ` [PATCH for-4.8] ipxe: update to newer commit [and 1 more messages] Ian Jackson
2016-10-12 14:09 ` Boris Ostrovsky
2016-10-12 14:14 ` Wei Liu
2016-10-12 14:16 ` Ian Jackson
2016-10-12 7:45 ` [PATCH for-4.8] ipxe: update to newer commit Jan Beulich
2016-10-11 21:11 ` Andrew Cooper
2016-10-11 21:17 ` Andrew Cooper
2016-10-12 7:50 ` Jan Beulich
2016-10-10 18:28 ` Juergen Schinker
2016-10-11 9:37 ` Wei Liu
2016-10-11 9:42 ` Juergen Schinker
2016-10-11 9:45 ` Wei Liu
2016-10-11 19:31 ` Juergen Schinker
2016-10-11 19:45 ` Konrad Rzeszutek Wilk
2016-10-12 9:27 ` Wei Liu
2016-10-12 21:03 ` Boris Ostrovsky
2016-10-13 9:04 ` Wei Liu
2016-10-13 9:10 ` Juergen Schinker
2016-10-13 9:29 ` Wei Liu [this message]
2016-10-13 10:02 ` Juergen Schinker
2016-10-13 14:53 ` Wei Liu
[not found] ` <1633715062.155.1476375972276.JavaMail.zimbra@homie.homelinux.net>
2016-10-13 16:45 ` Wei Liu
2016-10-13 19:58 ` ANNOUNCEMENT] Xen 4.8 RC2 FULL SUCCESS 13.10.16 Juergen Schinker
2016-10-13 9:32 ` [PATCH for-4.8] ipxe: update to newer commit Wei Liu
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=20161013092938.GB3687@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ba1020@homie.homelinux.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).