Building i386 jessie image

Building i386 jessie image

[Gernot Hillier]

[-- Attachment #1.1: Type: text/plain, Size: 1213 bytes --]

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 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 
buildTaskData (bitbake/lib/bb/cooker.py:683).

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

BTW1: Sorry 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 was so overwhelmed by all that colorful UI buttons that I couldn't 
find any subscribe link, only an option which notifies me by mail "less 
than 1 time a day".

BTW2: Currently, the distro configuration "debian-wheezy" implies ARM 
architecture. So shouldn'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 overriden in the bitbake call? If yes, how?

TIA!

--
Gernot

[-- Attachment #1.2: Type: text/html, Size: 1343 bytes --]

Re: Building i386 jessie image

[Gernot Hillier]

[-- Attachment #1.1: Type: text/plain, Size: 1557 bytes --]

Am Freitag, 3. März 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 ;) 
> ).
>
> 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 
> 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...)
 

>
> Before I go ahead and debug this, a short question: is it supposed to work 
> that (simple) way? Or would building another Debian version for another 
> arch require more work?
>
> BTW1: Sorry 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 was so overwhelmed by all that colorful UI buttons that I couldn't 
> find any subscribe link, only an option which notifies me by mail "less 
> than 1 time a day".
>
> BTW2: Currently, the distro configuration "debian-wheezy" implies ARM 
> architecture. So shouldn'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 overriden in the bitbake call? If yes, how?
>
> TIA!
>
> --
> Gernot
>

[-- Attachment #1.2: Type: text/html, Size: 1938 bytes --]

Re: Building i386 jessie image

[Baurzhan Ismagulov]

Hello Gernot,

On Fri, Mar 03, 2017 at 12:18:33AM -0800, 'Gernot Hillier' via isar-users wrote:
> I'm trying to build a Debian jessie i386 image with Isar (in 10 minutes ;) 
> ).

real 2m8s user 1m58s sys 13s on my SSD :) .


> 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 
> buildTaskData (bitbake/lib/bb/cooker.py:683).
> 
> Before I go ahead and debug this, a short question: is it supposed to work 
> that (simple) way? Or would building another Debian version for another 
> arch require more work?

It's more or less it, plus generalizing a couple of other bits. Please have a
look at https://github.com/ilbers/isar/tree/i386. It currently drops to the
initramfs shell, will have a look.


> BTW1: Sorry 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 was so overwhelmed by all that colorful UI buttons that I couldn't
> find any subscribe link, only an option which notifies me by mail "less
> than 1 time a day".

mailto:isar-users+subscribe@googlegroups.com.


> BTW2: Currently, the distro configuration "debian-wheezy" implies ARM
> architecture. So shouldn'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 overriden in the bitbake call? If yes, how?

Please see the i386 branch, we've moved that to local.conf / multiconfig.


With kind regards,
Baurzhan.

Re: Building i386 jessie image

[Baurzhan Ismagulov]

On Fri, Mar 03, 2017 at 11:58:55AM +0100, Baurzhan Ismagulov wrote:
> On Fri, Mar 03, 2017 at 12:18:33AM -0800, 'Gernot Hillier' via isar-users wrote:
> > I'm trying to build a Debian jessie i386 image with Isar
...
> Please have a
> look at https://github.com/ilbers/isar/tree/i386. It currently drops to the
> initramfs shell, will have a look.

Seems that QEMU's pc machine doesn't emulate mmcblk0. Using sda fixes the
problem, see the i386 branch.

time linux32 bitbake multiconfig:qemu-i386:isar-image-base
start_i386_vm

Does this work for you?

With kind regards,
Baurzhan.

Re: Building i386 jessie image

[Gernot Hillier]

[-- Attachment #1.1: Type: text/plain, Size: 2294 bytes --]

Hi Baurzhan!

Am Freitag, 3. März 2017 12:58:13 UTC+1 schrieb Baurzhan Ismagulov:
>
> Hello Gernot, 
>
> On Fri, Mar 03, 2017 at 12:18:33AM -0800, 'Gernot Hillier' via isar-users 
> wrote: 
> > 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 
> > buildTaskData (bitbake/lib/bb/cooker.py:683). 
> > 
> > Before I go ahead and debug this, a short question: is it supposed to 
> work 
> > that (simple) way? Or would building another Debian version for another 
> > arch require more work? 
>
> It's more or less it, plus generalizing a couple of other bits. Please 
> have a 
> look at https://github.com/ilbers/isar/tree/i386. It currently drops to 
> the 
> initramfs shell, will have a look. 
>

Ok, it seems I missed to add my config to local.conf.sample:BBMULTICONFIG. 
 

> > BTW1: Sorry 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 was so overwhelmed by all that colorful UI buttons that I 
> couldn't 
> > find any subscribe link, only an option which notifies me by mail "less 
> > than 1 time a day". 
>
> mailto:isar-users...@googlegroups.com <javascript:>. 
>

I see, but this still doesn't give me appropriate mail notifications - I 
got no notification about your answer, likely because you answered on the 
same day and Google doesn't want to spam me with more than one event per 
day... 
 

> > BTW2: Currently, the distro configuration "debian-wheezy" implies ARM 
> > architecture. So shouldn'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 overriden in the bitbake call? If yes, how? 
>
> Please see the i386 branch, we've moved that to local.conf / multiconfig. 
>

Thanks, works perfectly! Do you plan to merge i386 branch to master soon? 

I'm about to add amd64 and will hopefully send a pull request soon. 

--
Gernot

[-- Attachment #1.2: Type: text/html, Size: 3636 bytes --]

Stretch support (was: Re: Building i386 jessie image)

[Baurzhan Ismagulov]

Hello Gernot,

On Mon, Mar 06, 2017 at 07:33:53AM -0800, 'Gernot Hillier' via isar-users wrote:
> I'm about to add amd64 and will hopefully send a pull request soon. 

Thanks for the amd64 patches.

We've looked at Stretch. It seems that apt has a problem processing HTTP
redirects under some circumstances. Apt-get update gets 302 and continues
waiting. We'll report this problem to Debian as soon as we can reproduce it
manually.

Using a direct URI for stretch instead of httpredir works for us. Please let me
know whether this helps.

With kind regards,
Baurzhan.