From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6393183860533755904 Date: Fri, 3 Mar 2017 00:34:05 -0800 (PST) From: Gernot Hillier To: isar-users Message-Id: In-Reply-To: <7a00ea4d-2ed4-4b8e-b597-dbe44fd166da@googlegroups.com> References: <7a00ea4d-2ed4-4b8e-b597-dbe44fd166da@googlegroups.com> Subject: Re: Building i386 jessie image MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_417_1087186459.1488530045283" X-Google-Token: EP3U5MUFSge8StV08_c0 X-Google-IP: 79.218.166.254 X-TUID: ryRwesA03LoZ ------=_Part_417_1087186459.1488530045283 Content-Type: multipart/alternative; boundary="----=_Part_418_872693369.1488530045283" ------=_Part_418_872693369.1488530045283 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Freitag, 3. M=C3=A4rz 2017 09:18:33 UTC+1 schrieb Gernot Hillier: > > Hi there! > > I'm trying to build a Debian jessie i386 image with Isar (in 10 minutes ;= )=20 > ). > > So I did a bit of pattern matching and added the following files: > > meta-isar/conf/distro/debian-jessie.conf > meta-isar/conf/machine/qemui386.conf > meta-isar/conf/multiconfig/qemui386.conf > > with appropriate contents (I hope). > > But whatever I do, I always end up with a "KeyError: qemuintel" in=20 > buildTaskData (bitbake/lib/bb/cooker.py:683). > Sorry, the error certainly was "KeyError: qemui386" when trying to execute bitbake multiconfig:qemui386:isar-image-base (I mixed details from several tries...) =20 > > Before I go ahead and debug this, a short question: is it supposed to wor= k=20 > that (simple) way? Or would building another Debian version for another= =20 > arch require more work? > > BTW1: Sorry for this ugly message, but I didn't find a quick way to=20 > subscribe this Google thingie be as a normal ML. Can you tell me how this= =20 > works? I was so overwhelmed by all that colorful UI buttons that I couldn= 't=20 > find any subscribe link, only an option which notifies me by mail "less= =20 > than 1 time a day". > > BTW2: Currently, the distro configuration "debian-wheezy" implies ARM=20 > architecture. So shouldn't it be named debian-wheezy-arm then? Or does=20 > meta-isar/conf/distro/debian-wheezy.conf only define a default architectu= re=20 > which can be overriden in the bitbake call? If yes, how? > > TIA! > > -- > Gernot > ------=_Part_418_872693369.1488530045283 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Am Freitag, 3. M=C3=A4rz 2017 09:18:33 UTC+1 schrieb Gerno= t Hillier:
Hi = there!

I'm trying to build a Debian jessie i386 image with Isar = (in 10 minutes ;) ).

So I did a bit of pattern matching and added th= e following files:

meta-isar/conf/distro/debian-jessie.conf
= meta-isar/conf/machine/qemui386.conf
meta-isar/conf/multiconfig/qemui386.conf

with appropriate contents (I hope).

But whate= ver I do, I always end up with a "KeyError: qemuintel" in buildTa= skData (bitbake/lib/bb/cooker.py:683).

= Sorry, the error certainly was "KeyError: qemui386" when trying t= o execute

bitbake multiconfig:qemui386:isar-image-base

(I mix= ed details from several tries...)
=C2=A0

Before I go ahead and debug this, a= short question: is it supposed to work that (simple) way? Or would buildin= g another Debian version for another arch require more work?

BTW1: S= orry for this ugly message, but I didn't find a quick way to subscribe = this Google thingie be as a normal ML. Can you tell me how this works? I wa= s so overwhelmed by all that colorful UI buttons that I=20 couldn't find any subscribe link, only an option which notifies me by= =20 mail "less than 1 time a day".

BTW2: Currently, the distro= configuration "debian-wheezy" implies ARM architecture. So shoul= dn't it be named debian-wheezy-arm then? Or does meta-isar/conf/distro/= debian-wheezy.conf only define a default architecture which can be ove= rriden in the bitbake call? If yes, how?

TIA!

--
Gernot
------=_Part_418_872693369.1488530045283-- ------=_Part_417_1087186459.1488530045283--