public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Gernot Hillier <gernot.hillier@googlemail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Building i386 jessie image
Date: Mon, 6 Mar 2017 07:33:53 -0800 (PST)	[thread overview]
Message-ID: <32b0dd42-4db8-4e30-804a-edf4983a5236@googlegroups.com> (raw)
In-Reply-To: <20170303105852.GA3290@yssyq.radix50.net>


[-- 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 --]

  parent reply	other threads:[~2017-03-06 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  8:18 Gernot Hillier
2017-03-03  8:34 ` Gernot Hillier
2017-03-03 10:58 ` Baurzhan Ismagulov
2017-03-03 15:18   ` Baurzhan Ismagulov
2017-03-06 15:33   ` Gernot Hillier [this message]
2017-03-23  9:55     ` Stretch support (was: Re: Building i386 jessie image) Baurzhan Ismagulov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32b0dd42-4db8-4e30-804a-edf4983a5236@googlegroups.com \
    --to=gernot.hillier@googlemail.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox