WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] libelf.h and elfstructs.h

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] libelf.h and elfstructs.h
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 22 Dec 2008 10:36:05 +0000
Cc:
Delivery-date: Mon, 22 Dec 2008 02:36:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <494F76C7.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclkIReiCgLJNxZ6NUG5z1B3SI7P4A==
Thread-topic: [Xen-devel] libelf.h and elfstructs.h
User-agent: Microsoft-Entourage/12.14.0.081024
On 22/12/2008 10:15, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> What is the reason for these two to be part of the public (interface) headers?
> Using them anywhere outside of the Xen tree could easily conflict with the
> various other ELF headers used in different environments.

Gerd probably put them there for consumption, privately, by libxenguest.
Same as libxenguest hoovers up Xen's common/libelf.

I'd be happy to see those headers moved into include/xen/ or
include/xen/libelf, and have libxenguest grab them from there...

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>