default image won't build

default image won't build

[Francesco]

[-- Attachment #1: Type: text/plain, Size: 4149 bytes --]

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//
//Parsing recipes: 100% 
|###########################################################################################################################################| 
Time: 0:00:00//
//Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0 
skipped, 0 masked, 0 errors.//
//NOTE: Resolving any missing task queue dependencies//
//ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but 
/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb 
DEPENDS on or otherwise requires it)//
//ERROR: Required build target 'isar-image-base' has no buildable 
providers.//
//Missing or unbuildable dependency chain was: ['isar-image-base', 
'linux-image-${KERNEL_NAME}']/

So I added KERNEL_NAME ?= "armmp" to the local.conf but now I get 
another error:

/bitbake isar-image-base//
//Parsing recipes: 100% 
|###########################################################################################################################################| 
Time: 0:00:00//
//Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0 
skipped, 0 masked, 0 errors.//
//NOTE: Resolving any missing task queue dependencies//
//ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but 
/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb 
DEPENDS on or otherwise requires it)//
//ERROR: Required build target 'isar-image-base' has no buildable 
providers.//
//Missing or unbuildable dependency chain was: ['isar-image-base', 
'linux-image-${KERNEL_NAME}']//
//
//
//bitbake isar-image-base//
//Loading cache: 100% 
|#############################################################################################################################################| 
Time: 0:00:00//
//Loaded 110 entries from dependency cache.//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//Initialising tasks: 100% 
|########################################################################################################################################| 
Time: 0:00:00//
//NOTE: Executing RunQueue Tasks//
//ERROR: isar-image-base-1.0-r0 do_rootfs: Function failed: do_rootfs 
(log file is located at 
/mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
//ERROR: Logfile of failure stored in: 
/mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481//
//Log data follows://
//| DEBUG: Executing shell function do_rootfs//
//| sudo: no tty present and no askpass program specified//
//| WARNING: exit code 1 from a shell command.//
//| ERROR: Function failed: do_rootfs (log file is located at 
/mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
//ERROR: Task 
(/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs) 
failed with exit code '1'//
//NOTE: Tasks Summary: Attempted 6 tasks of which 5 didn't need to be 
rerun and 1 failed.//
//
//Summary: 1 task failed://
///mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs//
//Summary: There was 1 ERROR message shown, returning a non-zero exit 
code.//
/

the default tty in the conf/machine for qemuarm is set to ttyAMA0. My 
user is in the sudoers file as showed in the docs. I don't understand 
what I'm doing wrong here.

Hope you can help.

Frank


[-- Attachment #2: Type: text/html, Size: 5441 bytes --]

Re: default image won't build

[Jan Kiszka]

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).

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: default image won't build

[Claudius Heine]

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.

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

Re: default image won't build

[Alexander Smirnov]

Hello,

On 04/18/2018 01:50 PM, 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.
> 

it seems that you missed specificator for Debian distribution and machine.

Here:
https://github.com/ilbers/isar/blob/master/doc/user_manual.md#building-target-images-for-multiple-configurations

You may find the list of supported targets:

multiconfig:qemuarm-wheezy:isar-image-base
multiconfig:qemuarm-jessie:isar-image-base
multiconfig:qemuarm-stretch:isar-image-base
multiconfig:qemui386-jessie:isar-image-base
multiconfig:qemui386-stretch:isar-image-base
multiconfig:qemuamd64-jessie:isar-image-base
multiconfig:qemuamd64-stretch:isar-image-base
multiconfig:rpi-jessie:isar-image-base

Please try the one you want, just pass the whole line 
multiconfig:blablabla as the target for bitbake.

P.S. yeah, we know, that documentation is a bit outdated, will be fixed 
soon.

Alex

> My host OS is debian jessie.
> 
> Unfortunately when I try to build an image I get this error:
> 
> /bitbake isar-image-base//
> //Parsing recipes: 100% 
> |###########################################################################################################################################| 
> Time: 0:00:00//
> //Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0 
> skipped, 0 masked, 0 errors.//
> //NOTE: Resolving any missing task queue dependencies//
> //ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but 
> /mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb 
> DEPENDS on or otherwise requires it)//
> //ERROR: Required build target 'isar-image-base' has no buildable 
> providers.//
> //Missing or unbuildable dependency chain was: ['isar-image-base', 
> 'linux-image-${KERNEL_NAME}']/
> 
> So I added KERNEL_NAME ?= "armmp" to the local.conf but now I get 
> another error:
> 
> /bitbake isar-image-base//
> //Parsing recipes: 100% 
> |###########################################################################################################################################| 
> Time: 0:00:00//
> //Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0 
> skipped, 0 masked, 0 errors.//
> //NOTE: Resolving any missing task queue dependencies//
> //ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but 
> /mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb 
> DEPENDS on or otherwise requires it)//
> //ERROR: Required build target 'isar-image-base' has no buildable 
> providers.//
> //Missing or unbuildable dependency chain was: ['isar-image-base', 
> 'linux-image-${KERNEL_NAME}']//
> //
> //
> //bitbake isar-image-base//
> //Loading cache: 100% 
> |#############################################################################################################################################| 
> Time: 0:00:00//
> //Loaded 110 entries from dependency cache.//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //Initialising tasks: 100% 
> |########################################################################################################################################| 
> Time: 0:00:00//
> //NOTE: Executing RunQueue Tasks//
> //ERROR: isar-image-base-1.0-r0 do_rootfs: Function failed: do_rootfs 
> (log file is located at 
> /mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
> //ERROR: Logfile of failure stored in: 
> /mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481//
> //Log data follows://
> //| DEBUG: Executing shell function do_rootfs//
> //| sudo: no tty present and no askpass program specified//
> //| WARNING: exit code 1 from a shell command.//
> //| ERROR: Function failed: do_rootfs (log file is located at 
> /mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
> //ERROR: Task 
> (/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs) 
> failed with exit code '1'//
> //NOTE: Tasks Summary: Attempted 6 tasks of which 5 didn't need to be 
> rerun and 1 failed.//
> //
> //Summary: 1 task failed://
> ///mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs//
> //Summary: There was 1 ERROR message shown, returning a non-zero exit 
> code.//
> /
> 
> the default tty in the conf/machine for qemuarm is set to ttyAMA0. My 
> user is in the sudoers file as showed in the docs. I don't understand 
> what I'm doing wrong here.
> 
> Hope you can help.
> 
> Frank
> 
> -- 
> You received this message because you are subscribed to the Google 
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to isar-users+unsubscribe@googlegroups.com 
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to isar-users@googlegroups.com 
> <mailto:isar-users@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/isar-users/e50c604e-31c9-1d84-1370-aa3596778950%40dave.eu 
> <https://groups.google.com/d/msgid/isar-users/e50c604e-31c9-1d84-1370-aa3596778950%40dave.eu?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov

Re: default image won't build

[Jan Kiszka]

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
> 

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: default image won't build

[Francesco]

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.

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

Re: default image won't build

[Alexander Smirnov]

On 04/18/2018 01:50 PM, 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//
> //Parsing recipes: 100% 
> |###########################################################################################################################################| 
> Time: 0:00:00//
> //Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0 
> skipped, 0 masked, 0 errors.//
> //NOTE: Resolving any missing task queue dependencies//
> //ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but 
> /mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb 
> DEPENDS on or otherwise requires it)//
> //ERROR: Required build target 'isar-image-base' has no buildable 
> providers.//
> //Missing or unbuildable dependency chain was: ['isar-image-base', 
> 'linux-image-${KERNEL_NAME}']/
> 
> So I added KERNEL_NAME ?= "armmp" to the local.conf but now I get 
> another error:
> 
> /bitbake isar-image-base//
> //Parsing recipes: 100% 
> |###########################################################################################################################################| 
> Time: 0:00:00//
> //Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0 
> skipped, 0 masked, 0 errors.//
> //NOTE: Resolving any missing task queue dependencies//
> //ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but 
> /mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb 
> DEPENDS on or otherwise requires it)//
> //ERROR: Required build target 'isar-image-base' has no buildable 
> providers.//
> //Missing or unbuildable dependency chain was: ['isar-image-base', 
> 'linux-image-${KERNEL_NAME}']//
> //
> //
> //bitbake isar-image-base//
> //Loading cache: 100% 
> |#############################################################################################################################################| 
> Time: 0:00:00//
> //Loaded 110 entries from dependency cache.//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //NOTE: Resolving any missing task queue dependencies//
> //Initialising tasks: 100% 
> |########################################################################################################################################| 
> Time: 0:00:00//
> //NOTE: Executing RunQueue Tasks//
> //ERROR: isar-image-base-1.0-r0 do_rootfs: Function failed: do_rootfs 
> (log file is located at 
> /mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
> //ERROR: Logfile of failure stored in: 
> /mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481//
> //Log data follows://
> //| DEBUG: Executing shell function do_rootfs//
> //| sudo: no tty present and no askpass program specified//

This line usually means, that you have no /dev/pts folder mounted on 
build host. Also, don't remember why, but seems /proc should be also 
mounted.

> //| WARNING: exit code 1 from a shell command.//
> //| ERROR: Function failed: do_rootfs (log file is located at 
> /mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
> //ERROR: Task 
> (/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs) 
> failed with exit code '1'//
> //NOTE: Tasks Summary: Attempted 6 tasks of which 5 didn't need to be 
> rerun and 1 failed.//
> //
> //Summary: 1 task failed://
> ///mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs//
> //Summary: There was 1 ERROR message shown, returning a non-zero exit 
> code.//
> /
> 
> the default tty in the conf/machine for qemuarm is set to ttyAMA0. My 
> user is in the sudoers file as showed in the docs. I don't understand 
> what I'm doing wrong here.

Am I right that you can run 'sudo' without password?

Alex

> 
> Hope you can help.
> 
> Frank
> 
> -- 
> You received this message because you are subscribed to the Google 
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to isar-users+unsubscribe@googlegroups.com 
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to isar-users@googlegroups.com 
> <mailto:isar-users@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/isar-users/e50c604e-31c9-1d84-1370-aa3596778950%40dave.eu 
> <https://groups.google.com/d/msgid/isar-users/e50c604e-31c9-1d84-1370-aa3596778950%40dave.eu?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov

Re: default image won't build

[Claudius Heine]

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

Re: default image won't build

[Francesco]

[-- Attachment #1: Type: text/plain, Size: 2789 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 5175 bytes --]