From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6545739070330372096 X-Received: by 10.28.12.18 with SMTP id 18mr151178wmm.17.1524053549048; Wed, 18 Apr 2018 05:12:29 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.156.79 with SMTP id f76ls871491wme.9.gmail; Wed, 18 Apr 2018 05:12:28 -0700 (PDT) X-Google-Smtp-Source: AIpwx49cqOY10Z8C7SkfS8iHPOO0E0MCaCl3z34hzrYss7wvBU4inQx7z97G/jqXx5tRynTmb570 X-Received: by 10.28.16.20 with SMTP id 20mr163786wmq.14.1524053548579; Wed, 18 Apr 2018 05:12:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524053548; cv=none; d=google.com; s=arc-20160816; b=CJ8mNFrKSWDpZ6sux5qcKwqvhgYEz05qzVqjQHEENoEMxN8WFJBdITDr6Rx8ElLkmY sVMXGpXiiDhisQI3QRs6ydjEunvHr6AghQLCDlgAfxpZUxfGT314D9sQEoUyZ6ontVgh Ul6Og3hPFdR9va8Mq0PPjiiML+x/xKSIcYG1hOFzkYTig8P3kV48LJeuxQfSNbSSRS8A US9cBmwwRod0gh+zunAfZgC/lV9n5I5N0qZ5UratbarZE3nolQEyMFurZucL+V/Vu9kz dWseSnF+LI+0vjqFZpftmPHrkaZrpJbdW5Bu8kzgF8QS+CHbUwbFxyK0qW8GI8rK40GT Tjyw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:arc-authentication-results; bh=snD4Ppl4FzEMHhlq8QR/dhaXDAWAAetU6GMMXbRDW38=; b=GH2gvvewwFOFPepuT30xaGeGhfWP325Qod12w4BZIOaMv0ofWy2/NU4zCH6hDbNj4D hxYbD5uuirkaYJ0cCYU7o2oSd89ixcwjbrwiGwkIbhpGM+nqTBPFa9sc/NzijrUHXbSl abTZuatc/gbFbn9eQHmK/mTNPmai8UTh4k1VuL9QyuM9x1Xs5uoB2WyUacQXDQLWQuni ZcjLZYPRbihrShU/ko9LlT8ZrxHMkaqx56Ba/PTY8w/XmpNs3dZbYS5ya2eCDzX+b5Uz IY88Y4H1v4GzLqlbqdn1Z3V+ixjcSi7X2nuuwYtdrkrFQuxTp7OEJz0WT+/61PWDrSTf Gslw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of fdprnd@dave.eu designates 185.100.109.150 as permitted sender) smtp.mailfrom=fdprnd@dave.eu Return-Path: Received: from mx.dave-tech.it (mx.dave-tech.it. [185.100.109.150]) by gmr-mx.google.com with ESMTP id t10si64441wmh.0.2018.04.18.05.12.28 for ; Wed, 18 Apr 2018 05:12:28 -0700 (PDT) Received-SPF: pass (google.com: domain of fdprnd@dave.eu designates 185.100.109.150 as permitted sender) client-ip=185.100.109.150; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of fdprnd@dave.eu designates 185.100.109.150 as permitted sender) smtp.mailfrom=fdprnd@dave.eu Received: from [127.0.0.1] (unknown [192.168.0.115]) by mx.dave-tech.it (Postfix) with ESMTPS id 0A56A85 for ; Wed, 18 Apr 2018 14:12:28 +0200 (CEST) Subject: Re: default image won't build To: isar-users@googlegroups.com References: <9887613b-04cd-8c7e-92ba-b488c061ce73@siemens.com> <8156753a-607d-1b8f-886d-de288b40a098@siemens.com> <2db4bb8c-3b68-e46a-f72c-1900efbeadc4@dave.eu> <07339c40-0938-84da-73f0-758c654b9707@siemens.com> From: Francesco Message-ID: Date: Wed, 18 Apr 2018 14:12:27 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <07339c40-0938-84da-73f0-758c654b9707@siemens.com> Content-Type: multipart/alternative; boundary="------------9F45191F09F068C6F53AE1C1" Content-Language: en-GB X-TUID: m+vF9+UQ1SE3 This is a multi-part message in MIME format. --------------9F45191F09F068C6F53AE1C1 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I managed to fix the issue. The problem was due to sudo as Alexander pointed out. For some reasons, sudo without password was not working correctly with that configuration provided in the docs. I added this line /user ALL=(ALL) NOPASSWD:ALL/ below the sudo group section in /etc/sudoers and then it started to work. I'm glad it has now been solved. Thank you all Frank On 18/04/2018 13:15, Claudius Heine wrote: > 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 >>>> >> > --------------9F45191F09F068C6F53AE1C1 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

I managed to fix the issue. The problem was due to sudo as Alexander pointed out. For some reasons, sudo without password was not working correctly with that configuration provided in the docs.

I added this line

user ALL=(ALL) NOPASSWD:ALL

below the sudo group section in /etc/sudoers and then it started to work.

I'm glad it has now been solved.
Thank you all

Frank

On 18/04/2018 13:15, Claudius Heine wrote:
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




--------------9F45191F09F068C6F53AE1C1--