Toolchain... Issues with systemd (probably)

Toolchain... Issues with systemd (probably)

[DAMARLA Satya Swaroop]

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

I think I had to open the issue as its not closed... Here is more
clarity....

The issue is I decided the problem may be with init_manager. I did two
builds one with sysvinit using traditional Poky distro and other one is
uisng systemd using new distribution which is different as we need a new
distribution for using systemd

.. I didno t get any errors when i build using *bitbake -c populate_sdk
rootfs-smartcpu* with sysvinit and got build errors using systemd...

Any possible resons what could have caused failure to build the toolchain?

Cheers,
Satya

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

Re: Toolchain... Issues with systemd (probably)

[Burton, Ross]

On 19 June 2013 13:08, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com> wrote:
> I think I had to open the issue as its not closed... Here is more
> clarity....
>
> The issue is I decided the problem may be with init_manager. I did two
> builds one with sysvinit using traditional Poky distro and other one is
> uisng systemd using new distribution which is different as we need a new
> distribution for using systemd
>
> .. I didno t get any errors when i build using bitbake -c populate_sdk
> rootfs-smartcpu with sysvinit and got build errors using systemd...
>
> Any possible resons what could have caused failure to build the toolchain?

It really helps when you tell us what the errors are.

Note that changing DISTRO_FEATURES in an existing build directory
isn't supported and may well cause problems.

Ross

Re: Toolchain... Issues with systemd (probably)

[DAMARLA Satya Swaroop]

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

Yes... I thought the same and so, I made two build directories , one for
sysvinit and the other for systemd and the errors I get abosulte no error
when I try to *populate_sdk* under sysvinit but I get the following errors
when I run the same under systemd.

*| The following packages have unmet dependencies:*
*|  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed*
*|             Recommends: libusb-dev but it is not installable*
*|             Recommends: module-init-tools-dev but it is not installable*
*|             Recommends: libkmod-dev but it is not installable*
*| E: Unable to correct problems, you have held broken packages.*
*| DEBUG: Python function do_populate_sdk finished*
*| ERROR: Function failed: populate_sdk_image (log file is located at
/home/damarla/openYocto/poky/buildSmartCPUsystemd/tmp/work/smartcpu-poky-linux-gnueabi/rootfs-smartcpu-sdk/1.0-r0/temp/log.do_populate_sdk.17015)
*
*ERROR: Task 10
(/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
rootfs-smartcpu-sdk.bb, do_populate_sdk) failed with exit code '1'*
*NOTE: Tasks Summary: Attempted 4961 tasks of which 4960 didn't need to be
rerun and 1 failed.*
*
*
*Summary: 1 task failed:*
*  /home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
rootfs-smartcpu-sdk.bb, do_populate_sdk*
*Summary: There was 1 ERROR message shown, returning a non-zero exit code.*
*
*
* *I don't understand why I dont get an error with sysvinit and get an
error here....


On Wed, Jun 19, 2013 at 2:11 PM, Burton, Ross <ross.burton@intel.com> wrote:

> On 19 June 2013 13:08, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com>
> wrote:
> > I think I had to open the issue as its not closed... Here is more
> > clarity....
> >
> > The issue is I decided the problem may be with init_manager. I did two
> > builds one with sysvinit using traditional Poky distro and other one is
> > uisng systemd using new distribution which is different as we need a new
> > distribution for using systemd
> >
> > .. I didno t get any errors when i build using bitbake -c populate_sdk
> > rootfs-smartcpu with sysvinit and got build errors using systemd...
> >
> > Any possible resons what could have caused failure to build the
> toolchain?
>
> It really helps when you tell us what the errors are.
>
> Note that changing DISTRO_FEATURES in an existing build directory
> isn't supported and may well cause problems.
>
> Ross
>

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

Re: Toolchain... Issues with systemd (probably)

[DAMARLA Satya Swaroop]

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

Any reasons why toolchains compile wihtout any issues on sysvinit and not
with systemd?


On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop <
swaroop.damarla@gmail.com> wrote:

> Yes... I thought the same and so, I made two build directories , one for
> sysvinit and the other for systemd and the errors I get abosulte no error
> when I try to *populate_sdk* under sysvinit but I get the following
> errors when I run the same under systemd.
>
> *| The following packages have unmet dependencies:*
> *|  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed*
> *|             Recommends: libusb-dev but it is not installable*
> *|             Recommends: module-init-tools-dev but it is not installable
> *
> *|             Recommends: libkmod-dev but it is not installable*
> *| E: Unable to correct problems, you have held broken packages.*
> *| DEBUG: Python function do_populate_sdk finished*
> *| ERROR: Function failed: populate_sdk_image (log file is located at
> /home/damarla/openYocto/poky/buildSmartCPUsystemd/tmp/work/smartcpu-poky-linux-gnueabi/rootfs-smartcpu-sdk/1.0-r0/temp/log.do_populate_sdk.17015)
> *
> *ERROR: Task 10
> (/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
> rootfs-smartcpu-sdk.bb, do_populate_sdk) failed with exit code '1'*
> *NOTE: Tasks Summary: Attempted 4961 tasks of which 4960 didn't need to
> be rerun and 1 failed.*
> *
> *
> *Summary: 1 task failed:*
> *  /home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
> rootfs-smartcpu-sdk.bb, do_populate_sdk*
> *Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> *
> *
> *
> * *I don't understand why I dont get an error with sysvinit and get an
> error here....
>
>
> On Wed, Jun 19, 2013 at 2:11 PM, Burton, Ross <ross.burton@intel.com>wrote:
>
>> On 19 June 2013 13:08, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com>
>> wrote:
>> > I think I had to open the issue as its not closed... Here is more
>> > clarity....
>> >
>> > The issue is I decided the problem may be with init_manager. I did two
>> > builds one with sysvinit using traditional Poky distro and other one is
>> > uisng systemd using new distribution which is different as we need a new
>> > distribution for using systemd
>> >
>> > .. I didno t get any errors when i build using bitbake -c populate_sdk
>> > rootfs-smartcpu with sysvinit and got build errors using systemd...
>> >
>> > Any possible resons what could have caused failure to build the
>> toolchain?
>>
>> It really helps when you tell us what the errors are.
>>
>> Note that changing DISTRO_FEATURES in an existing build directory
>> isn't supported and may well cause problems.
>>
>> Ross
>>
>
>

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

Re: Toolchain... Issues with systemd (probably)

[Khem Raj]

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


On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop <satyaswaroop.damarla@gmail.com> wrote:

> Any reasons why toolchains compile wihtout any issues on sysvinit and not with systemd?
> 
> 
> On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com> wrote:
> Yes... I thought the same and so, I made two build directories , one for sysvinit and the other for systemd and the errors I get abosulte no error when I try to populate_sdk under sysvinit but I get the following errors when I run the same under systemd.
> 
> | The following packages have unmet dependencies:
> |  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed
> |             Recommends: libusb-dev but it is not installable
> |             Recommends: module-init-tools-dev but it is not installable
> |             Recommends: libkmod-dev but it is not installable
> | E: Unable to correct problems, you have held broken packages.


it seems you did not choose systemd as provider for udev. You should do that when you use systemd


> | DEBUG: Python function do_populate_sdk finished
> | ERROR: Function failed: populate_sdk_image (log file is located at /home/damarla/openYocto/poky/buildSmartCPUsystemd/tmp/work/smartcpu-poky-linux-gnueabi/rootfs-smartcpu-sdk/1.0-r0/temp/log.do_populate_sdk.17015)
> ERROR: Task 10 (/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/rootfs-smartcpu-sdk.bb, do_populate_sdk) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 4961 tasks of which 4960 didn't need to be rerun and 1 failed.
> 
> Summary: 1 task failed:
>   /home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/rootfs-smartcpu-sdk.bb, do_populate_sdk
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
>  I don't understand why I dont get an error with sysvinit and get an error here....
> 
> 
> On Wed, Jun 19, 2013 at 2:11 PM, Burton, Ross <ross.burton@intel.com> wrote:
> On 19 June 2013 13:08, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com> wrote:
> > I think I had to open the issue as its not closed... Here is more
> > clarity....
> >
> > The issue is I decided the problem may be with init_manager. I did two
> > builds one with sysvinit using traditional Poky distro and other one is
> > uisng systemd using new distribution which is different as we need a new
> > distribution for using systemd
> >
> > .. I didno t get any errors when i build using bitbake -c populate_sdk
> > rootfs-smartcpu with sysvinit and got build errors using systemd...
> >
> > Any possible resons what could have caused failure to build the toolchain?
> 
> It really helps when you tell us what the errors are.
> 
> Note that changing DISTRO_FEATURES in an existing build directory
> isn't supported and may well cause problems.
> 
> Ross
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


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

Re: Toolchain... Issues with systemd (probably)

[DAMARLA Satya Swaroop]

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

Hi Khem,

May I ask you where I have to set that because I dont see anything like
sysvinit has been set ... would be greatfull if you can tell me that

Greets,
Satya


On Thu, Jun 20, 2013 at 9:29 AM, Khem Raj <raj.khem@gmail.com> wrote:

>
> On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop <
> satyaswaroop.damarla@gmail.com> wrote:
>
> Any reasons why toolchains compile wihtout any issues on sysvinit and not
> with systemd?
>
>
> On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop <
> swaroop.damarla@gmail.com> wrote:
>
>> Yes... I thought the same and so, I made two build directories , one for
>> sysvinit and the other for systemd and the errors I get abosulte no error
>> when I try to *populate_sdk* under sysvinit but I get the following
>> errors when I run the same under systemd.
>>
>> *| The following packages have unmet dependencies:*
>> *|  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed*
>> *|             Recommends: libusb-dev but it is not installable*
>> *|             Recommends: module-init-tools-dev but it is not
>> installable*
>> *|             Recommends: libkmod-dev but it is not installable*
>> *| E: Unable to correct problems, you have held broken packages.*
>>
>
>
> it seems you did not choose systemd as provider for udev. You should do
> that when you use systemd
>
>
> *| DEBUG: Python function do_populate_sdk finished*
>> *| ERROR: Function failed: populate_sdk_image (log file is located at
>> /home/damarla/openYocto/poky/buildSmartCPUsystemd/tmp/work/smartcpu-poky-linux-gnueabi/rootfs-smartcpu-sdk/1.0-r0/temp/log.do_populate_sdk.17015)
>> *
>> *ERROR: Task 10
>> (/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
>> rootfs-smartcpu-sdk.bb, do_populate_sdk) failed with exit code '1'*
>>  *NOTE: Tasks Summary: Attempted 4961 tasks of which 4960 didn't need to
>> be rerun and 1 failed.*
>> *
>> *
>> *Summary: 1 task failed:*
>> *  /home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
>> rootfs-smartcpu-sdk.bb, do_populate_sdk*
>> *Summary: There was 1 ERROR message shown, returning a non-zero exit
>> code.*
>> *
>> *
>> * *I don't understand why I dont get an error with sysvinit and get an
>> error here....
>>
>>
>> On Wed, Jun 19, 2013 at 2:11 PM, Burton, Ross <ross.burton@intel.com>wrote:
>>
>>> On 19 June 2013 13:08, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com>
>>> wrote:
>>> > I think I had to open the issue as its not closed... Here is more
>>> > clarity....
>>> >
>>> > The issue is I decided the problem may be with init_manager. I did two
>>> > builds one with sysvinit using traditional Poky distro and other one is
>>> > uisng systemd using new distribution which is different as we need a
>>> new
>>> > distribution for using systemd
>>> >
>>> > .. I didno t get any errors when i build using bitbake -c populate_sdk
>>> > rootfs-smartcpu with sysvinit and got build errors using systemd...
>>> >
>>> > Any possible resons what could have caused failure to build the
>>> toolchain?
>>>
>>> It really helps when you tell us what the errors are.
>>>
>>> Note that changing DISTRO_FEATURES in an existing build directory
>>> isn't supported and may well cause problems.
>>>
>>> Ross
>>>
>>
>>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>

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

Re: Toolchain... Issues with systemd (probably)

[Paul Eggleton]

On Thursday 20 June 2013 00:29:23 Khem Raj wrote:
> On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop
> <satyaswaroop.damarla@gmail.com> wrote:
> > Any reasons why toolchains compile wihtout any issues on sysvinit and not
> > with systemd?
> > 
> > 
> > On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop
> > <swaroop.damarla@gmail.com> wrote: Yes... I thought the same and so, I
> > made two build directories , one for sysvinit and the other for systemd
> > and the errors I get abosulte no error when I try to populate_sdk under
> > sysvinit but I get the following errors when I run the same under
> > systemd.> 
> > | The following packages have unmet dependencies:
> > |  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed
> > |  
> > |             Recommends: libusb-dev but it is not installable
> > |             Recommends: module-init-tools-dev but it is not installable
> > |             Recommends: libkmod-dev but it is not installable
> > | 
> > | E: Unable to correct problems, you have held broken packages.
> 
> it seems you did not choose systemd as provider for udev. You should do that
> when you use systemd

default-providers.inc already does this so you should not need to:

meta/conf/distro/include/default-providers.inc:PREFERRED_PROVIDER_udev ?= 
"${@base_contains('DISTRO_FEATURES','systemd','systemd','udev',d)}"

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Toolchain... Issues with systemd (probably)

[DAMARLA Satya Swaroop]

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

Yeah.. I checked it and its true. In the errror its totally different issue

*| The following packages have unmet dependencies:*
*|  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed*
*|             Recommends: libusb-dev but it is not installable*
*|             Recommends: module-init-tools-dev but it is not installable*
*|             Recommends: libkmod-dev but it is not installable*
*| E: Unable to correct problems, you have held broken packages.*
*| DEBUG: Python function do_populate_sdk finished*
*| ERROR: Function failed: populate_sdk_image (log file is located at
/home/damarla/openYocto/poky/buildSmartCPUsystemd/tmp/work/smartcpu-poky-linux-gnueabi/rootfs-smartcpu-sdk/1.0-r0/temp/log.do_populate_sdk.6675)
*
*ERROR: Task 10
(/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/
rootfs-smartcpu-sdk.bb, do_populate_sdk) failed with exit code '1'*
*NOTE: Tasks Summary: Attempted 4961 tasks of which 4596 didn't need to be
rerun and 1 failed.*

The udev version to ve installed is 182-r7 bu I dont understand why
1:204-r0 is trying to get installed..


On Thu, Jun 20, 2013 at 10:31 AM, Paul Eggleton <
paul.eggleton@linux.intel.com> wrote:

> On Thursday 20 June 2013 00:29:23 Khem Raj wrote:
> > On Jun 20, 2013, at 12:12 AM, DAMARLA Satya Swaroop
> > <satyaswaroop.damarla@gmail.com> wrote:
> > > Any reasons why toolchains compile wihtout any issues on sysvinit and
> not
> > > with systemd?
> > >
> > >
> > > On Wed, Jun 19, 2013 at 3:11 PM, DAMARLA Satya Swaroop
> > > <swaroop.damarla@gmail.com> wrote: Yes... I thought the same and so, I
> > > made two build directories , one for sysvinit and the other for systemd
> > > and the errors I get abosulte no error when I try to populate_sdk under
> > > sysvinit but I get the following errors when I run the same under
> > > systemd.>
> > > | The following packages have unmet dependencies:
> > > |  udev-dev : Depends: udev (= 182-r7) but 1:204-r0 is to be installed
> > > |
> > > |             Recommends: libusb-dev but it is not installable
> > > |             Recommends: module-init-tools-dev but it is not
> installable
> > > |             Recommends: libkmod-dev but it is not installable
> > > |
> > > | E: Unable to correct problems, you have held broken packages.
> >
> > it seems you did not choose systemd as provider for udev. You should do
> that
> > when you use systemd
>
> default-providers.inc already does this so you should not need to:
>
> meta/conf/distro/include/default-providers.inc:PREFERRED_PROVIDER_udev ?=
> "${@base_contains('DISTRO_FEATURES','systemd','systemd','udev',d)}"
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>

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

Re: Toolchain... Issues with systemd (probably)

[Burton, Ross]

On 20 June 2013 10:07, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com> wrote:
> The udev version to ve installed is 182-r7 bu I dont understand why 1:204-r0
> is trying to get installed..

This is because your deploy directory contains the systemd "udev"
package, which is version 204 and so newer than the sysvinit "udev"
package, version 182.  This is why we say that switching distro
features in an existing build directory isn't supported.

If you delete your tmp directory it will rebuild everything quickly
using the sstate-cache (don't delete that!).

Ross

Re: Toolchain... Issues with systemd (probably)

[DAMARLA Satya Swaroop]

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

I think you guys are right.... and now I am able to build the toolchain
perfectly....


On Thu, Jun 20, 2013 at 12:06 PM, Burton, Ross <ross.burton@intel.com>wrote:

> On 20 June 2013 10:07, DAMARLA Satya Swaroop <swaroop.damarla@gmail.com>
> wrote:
> > The udev version to ve installed is 182-r7 bu I dont understand why
> 1:204-r0
> > is trying to get installed..
>
> This is because your deploy directory contains the systemd "udev"
> package, which is version 204 and so newer than the sysvinit "udev"
> package, version 182.  This is why we say that switching distro
> features in an existing build directory isn't supported.
>
> If you delete your tmp directory it will rebuild everything quickly
> using the sstate-cache (don't delete that!).
>
> Ross
>

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