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
 
   
 

xci-devel

Re: [Xci-devel] XCI repositories

To: Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxxx>
Subject: Re: [Xci-devel] XCI repositories
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Tue, 22 Sep 2009 19:54:58 +0300
Cc: "xci-devel@xxxxxxxxxxxxxxxxxxx" <xci-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 Sep 2009 09:55:01 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=vXQO2IKpC/mlAN4pFBtBtaPDmKLIf4k88w0s0GllLJA=; b=Gj6OVPbqAdk2c1q21NN2UBqL72qH+McJS9doQGjOJ/QqgF/uCcuryqqpGdQsd/rsw7 zafupec3RlFfsVyJfjuwUWj/lNrlPNMOyQNvqrGfKIESYlaH3jwND07l6OIn8BCwMwmm IJ3qsjWkqLWas3nz4S20T2eI6BmlTkbtMQDw8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KnV60OPX93aAyCKYhqGIdP5mXjI1aLshlli2FxRv7ByMYr5cYH/Bqr2+vU37G7/Dz1 XCIi71Tvc3t46FLKIfTNW2us2UvZhXf48Vj8kxqOhfJqVqm5g+/jqS2OKgAi3ibJsI3F ydfQ+zs58dicZS3ork0fkGha/WArwXgzWOqZM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AB8FF5B.20906@xxxxxxxxxxxxx>
List-archive: <http://lists.xensource.com/archives/html/xci-devel>
List-help: <mailto:xci-devel-request@lists.xensource.com?subject=help>
List-id: xci-devel.lists.xensource.com
List-post: <mailto:xci-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xci-devel>, <mailto:xci-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xci-devel>, <mailto:xci-devel-request@lists.xensource.com?subject=unsubscribe>
References: <d1ee18fa0909170727q7c3c71bale618974320d9731c@xxxxxxxxxxxxxx> <4AB24A0E.2060800@xxxxxxxxxxxxx> <8686c3cd0909170752h77ceb9b7s4db4909d193832a@xxxxxxxxxxxxxx> <4AB8FF5B.20906@xxxxxxxxxxxxx>
Sender: xci-devel-bounces@xxxxxxxxxxxxxxxxxxx
OK.

I have a few more questions/problems:

1. I'm still trying to build teh XCI for USB, and it's not working for
me at all. Could you please support a downloadable binary or something
like this, which i can just generate the XCI usb from? without the
need to build the whole XCI?

2.  All my builds (on a 32 bit Ubuntu) fail, with the following (last) output:
...
nclient_usb/root/lib/libgcc_s*
mkdir -p /root/xci/build/project_build_i686/xenclient_usb/autotools-stamps
touch 
/root/xci/build/project_build_i686/xenclient_usb/autotools-stamps/gcc_libs_target_installed
wget --passive-ftp -nd   -P /root/xci/build/dl
http://avr32linux.org/twiki/pub/Main/LibAio//libaio-0.3.106-avr32.tar.bz2
--2009-09-22 12:52:57--
http://avr32linux.org/twiki/pub/Main/LibAio//libaio-0.3.106-avr32.tar.bz2
Resolving avr32linux.org... 158.38.152.244
Connecting to avr32linux.org|158.38.152.244|:80...
"

It looks like avr32linux.org:80 isn't alive...
Can u please help me with this?

Tom


On Tue, Sep 22, 2009 at 7:46 PM, Vincent Hanquez
<vincent.hanquez@xxxxxxxxxxxxx> wrote:
> Tom Rotenberg wrote:
>>
>> BTW - does the XCI build system, now supports building on a 64 bit
>> machine?
>>
>
> I'm afraid is still doesn't; it could be possible to build a glibc target on
> buildroot that would probably give less problems than the uclibc target.
>
> I think requiring a 32 bits chroot at the moment is the best option. it
> doesn't support
> less features than building on 64 bits anyway (just a bit more pain for the
> setup), so i think our priority for this is pretty low. until we switch to
> openembedded, which we're looking to do at some point AFAIK.
>
> --
> Vincent Hanquez
>

_______________________________________________
Xci-devel mailing list
Xci-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xci-devel

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