From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Francesco <fdprnd@dave.eu>, isar-users@googlegroups.com
Subject: Re: default image won't build
Date: Wed, 18 Apr 2018 13:15:10 +0200 [thread overview]
Message-ID: <07339c40-0938-84da-73f0-758c654b9707@siemens.com> (raw)
In-Reply-To: <2db4bb8c-3b68-e46a-f72c-1900efbeadc4@dave.eu>
Hi Frank,
On 2018-04-18 13:08, Francesco wrote:
> Thanks for your replies. I just checked the BBMULTICONF variable in
> local.conf and it is there.
>
> Unfortunately If i now try to run bitbake
> multiconfig:qemuarm-jessie:isar-image-base I stil get the same error.
Your error does look interesting. I would think that somehow your
sudoers setting doesn't work correctly. Maybe try that out. It shouldn't
ask for your password.
Otherwise I can suggest building isar inside a container such as:
https://hub.docker.com/r/kasproject/kas-isar/
The system settings and basic dependencies are already setup there.
You just need to start it like this:
sudo docker run -v $(pwd):/mnt:rw -e USER_ID=$(id -u)
--cap-add=SYS_ADMIN --cap-add=MKNOD --security-opt=seccomp:unconfined
--privileged --device $(sudo /sbin/losetup -f) -rm -ti
kasproject/kas-isar:latest bash
And it should work.
Cheers,
Claudius
>
> Frank
>
>
> On 18/04/2018 13:03, Jan Kiszka wrote:
>> On 2018-04-18 13:01, Claudius Heine wrote:
>>> Hi,
>>>
>>> On 2018-04-18 12:56, [ext] Jan Kiszka wrote:
>>>> On 2018-04-18 12:50, Francesco wrote:
>>>>> Hello everyone,
>>>>>
>>>>> I'm new to isar and today I made an attempt to build the default image
>>>>> with it. I installed all the host tools necessary as it is written in
>>>>> the docs. Then I followed strictly the doc/user_manual.
>>>>>
>>>>> My host OS is debian jessie.
>>>>>
>>>>> Unfortunately when I try to build an image I get this error:
>>>>>
>>>>> /bitbake isar-image-base//
>>>> In that case, you are not using the multiconfig files Isar ships and
>>>> have to replicate all required settings into your local.conf. I would
>>>> rather recommend
>>>>
>>>> bitbake multiconfig:qemuarm-jessie:isar-image-base
>>>>
>>>> That will work (is also part of CI).
>>> You also need to set the BBMULTICONF variable in local.conf.
>>>
>> Good point! I'm too much used to kas descriptions by now. ;)
>>
>> Jan
>>
>>> Maybe just follow this:
>>>
>>> https://github.com/ilbers/isar/blob/53ed253/doc/user_manual.md#building-target-images-for-multiple-configurations
>>>
>>>
>>>
>>> And just use one configuration.
>>>
>>> The documentation about 'One configuration' is not really up-to-date.
>>>
>>> Cheers,
>>> Claudius
>>>
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2018-04-18 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 10:50 Francesco
2018-04-18 10:56 ` Jan Kiszka
2018-04-18 11:01 ` Claudius Heine
2018-04-18 11:03 ` Jan Kiszka
2018-04-18 11:08 ` Francesco
2018-04-18 11:15 ` Claudius Heine [this message]
2018-04-18 12:12 ` Francesco
2018-04-18 11:01 ` Alexander Smirnov
2018-04-18 11:14 ` Alexander Smirnov
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=07339c40-0938-84da-73f0-758c654b9707@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=fdprnd@dave.eu \
--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