All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Lalancette <clalance@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH]: Implement bzip2 and LZMA loaders / fixed patch for Xen 3.4.1
Date: Fri, 21 Aug 2009 11:42:46 +0200	[thread overview]
Message-ID: <4A8E6C16.1030908@redhat.com> (raw)
In-Reply-To: <C6B4299D.129E4%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> On 21/08/2009 10:22, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
> 
>>> Okay, I tested and fixed the stubdom case, so hopefully c/s 20104 will
>>> actually work for you.
>>>
>> xen-unstable "make tools && make stubdom" compiles for me with and without
>> libbz2-devel/liblzma-devel installed.
>>
>> But even when I have liblzma-devel installed it doesn't seem to use it.
>> ie. I only see -DHAVE_BZLIB in the build log and libxenguest.so.3.4.0 gets
>> only linked against -lbz2.
>>
>> Investigating more..
> 
> With that package installed, do you have a header /usr/include/lzma.h, or
> otherwise have lzma.h on the standard include path? If not then we're doing
> the right thing, since Chris's patch wants to #include <lzma.h>. If it is,
> then the has_header lzma.h check in the libxc Makefile is broken somehow.

Hm, there's also a somewhat confusing situation with LZMA.  I'm not sure I
completely understand it, but from what I can tell the lzma.h header file should
be coming from the new "xz" project, not from the lzma project.  That is, on my
Fedora 10 box, in order to get LZMA support compiled, I needed to install the
xz-devel package; lzma-devel was not sufficient.

-- 
Chris Lalancette

  reply	other threads:[~2009-08-21  9:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  7:47 [PATCH]: Implement bzip2 and LZMA loaders Chris Lalancette
2009-08-20 18:34 ` [PATCH]: Implement bzip2 and LZMA loaders / fixed patch for Xen 3.4.1 Pasi Kärkkäinen
2009-08-20 20:14   ` Pasi Kärkkäinen
2009-08-20 21:15     ` Keir Fraser
2009-08-20 21:27       ` Keir Fraser
2009-08-21  9:22         ` Pasi Kärkkäinen
2009-08-21  9:38           ` Keir Fraser
2009-08-21  9:42             ` Chris Lalancette [this message]
2009-08-21  9:45               ` Pasi Kärkkäinen
2009-08-21  9:43             ` Keir Fraser
2009-08-21  9:44           ` Pasi Kärkkäinen
2009-08-21  9:43     ` Gerd Hoffmann
2009-08-21  9:49       ` Pasi Kärkkäinen
2009-08-21  9:54         ` Keir Fraser
2009-08-21 10:13           ` Keir Fraser
2009-08-21 10:57             ` Pasi Kärkkäinen
2009-08-21 13:09               ` Keir Fraser
2009-08-21 14:01                 ` Pasi Kärkkäinen
2009-08-21 15:03                   ` Pasi Kärkkäinen
2009-08-21 15:06                     ` Pasi Kärkkäinen
2009-08-21 15:58                   ` Keir Fraser
2009-08-21 20:12             ` Pasi Kärkkäinen
2009-08-21 21:22               ` Pasi Kärkkäinen
2009-08-22  6:56                 ` Keir Fraser
2009-08-24 14:04                 ` Stefano Stabellini
2009-08-25 15:23                   ` Pasi Kärkkäinen
2009-09-01 19:08                     ` [PATCH]: Implement bzip2 and LZMA loaders / xen-unstable stubdom pvgrub support Pasi Kärkkäinen
2009-10-08 20:08                       ` Pasi Kärkkäinen
2009-10-13 16:17                         ` Stefano Stabellini

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=4A8E6C16.1030908@redhat.com \
    --to=clalance@redhat.com \
    --cc=keir.fraser@eu.citrix.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.