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/
Home Products Support Community News


[Xen-devel] Re: [PATCH 1/4] xen: Clean up build system

To: Alexander Graf <agraf@xxxxxxx>
Subject: [Xen-devel] Re: [PATCH 1/4] xen: Clean up build system
From: Jan Kiszka <jan.kiszka@xxxxxx>
Date: Tue, 21 Jun 2011 09:27:40 +0200
Cc: Anthony PERARD <anthony.perard@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, qemu-devel@xxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 21 Jun 2011 00:28:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A1F35AD8-AF73-4A75-BE92-AD1E9988C34B@xxxxxxx>
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>
References: <cover.1308637593.git.jan.kiszka@xxxxxx> <9e6a385a5db82c11b78f87b207fa70136f0c2855.1308637593.git.jan.kiszka@xxxxxx> <56EF9EC1-2FA8-4579-BFDF-8E7C2895185E@xxxxxxx> <4E0046F7.9010805@xxxxxx> <A1F35AD8-AF73-4A75-BE92-AD1E9988C34B@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv: Gecko/20080226 SUSE/ Thunderbird/ Mnenhy/
On 2011-06-21 09:26, Alexander Graf wrote:
> On 21.06.2011, at 09:23, Jan Kiszka wrote:
>> On 2011-06-21 09:21, Alexander Graf wrote:
>>> On 21.06.2011, at 08:26, Jan Kiszka wrote:
>>>> From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
>>>> Introduce CONFIG_XEN_BACKEND so that this new config solely controls the
>>>> target-independent backend build and CONFIG_XEN can focus on per-target
>>>> building.
>>> What's the incentive here? I very much doubt we'll ever want to support xen 
>>> on !x86. In fact, the better solution would probably be to just move every 
>>> build component to x86 specific code.
>> I doubt that as well. But keeping the backend centrals prevent building
>> them twice (for i386 and x86_64).
> How can we not build them twice without risking that target_ulong breaks 
> somewhere along the way?

Because the backends don't depend on that. And we already build them
only once, your your logs. :)


Attachment: signature.asc
Description: OpenPGP digital signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>