* in-tree module dependency
@ 2019-09-04 9:56 Matteo Facchinetti
2019-09-04 13:54 ` Khem Raj
0 siblings, 1 reply; 6+ messages in thread
From: Matteo Facchinetti @ 2019-09-04 9:56 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Hi,
I have a problem with a custom kernel module's recipe that depends to an
other module (in-tree).
My kernel module recipes built seems OK, but I have a problem when doing
the rootfs image stage.
Error:
Problem: package packagegroup-console-sirlinux-1.0-r0.0.noarch requires
canopen-sync, but none of the providers can be installed
- package canopen-sync-git-r0.2.neo_sirius requires
kernel-module-canopen-sync-4.9.51-yocto-standard, but none of the providers
can be installed
- conflicting requests
- nothing provides kernel-module-xeno-can-4.9.51-yocto-standard needed by
kernel-module-canopen-sync-4.9.51-yocto-standard-git-r0.2.neo_sirius
ERROR: sirlinux4-image-qt4e-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/workspace/neo-sirius_sirlinux4/build/tmp/work/neo_sirius-poky-linux-gnueabi/sirlinux4-image-qt4e/1.0-r0/temp/log.do_rootfs.9126
ERROR: Task
(/workspace/neo-sirius_sirlinux4/meta-sirlinux/recipes-qt4/images/sirlinux4-image-qt4e.bb:do_rootfs)
failed with exit code '1'
I don't understand how exactly the modules dependencies works...
Initially, I suppose that PROVIDES variable was updated automatically with
the correct modules names when compiled like module from kernel but now, I
don't know if I have to specify it manually or is there any other way?
Regards,
Matteo
[-- Attachment #2: Type: text/html, Size: 1449 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: in-tree module dependency
2019-09-04 9:56 in-tree module dependency Matteo Facchinetti
@ 2019-09-04 13:54 ` Khem Raj
2019-09-04 14:10 ` Matteo Facchinetti
0 siblings, 1 reply; 6+ messages in thread
From: Khem Raj @ 2019-09-04 13:54 UTC (permalink / raw)
To: Matteo Facchinetti; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
On Wed, Sep 4, 2019 at 2:58 AM Matteo Facchinetti <
matteo.facchinetti@sirius-es.it> wrote:
> Hi,
>
> I have a problem with a custom kernel module's recipe that depends to an
> other module (in-tree).
> My kernel module recipes built seems OK, but I have a problem when doing
> the rootfs image stage.
>
> Error:
> Problem: package packagegroup-console-sirlinux-1.0-r0.0.noarch requires
> canopen-sync, but none of the providers can be installed
> - package canopen-sync-git-r0.2.neo_sirius requires
> kernel-module-canopen-sync-4.9.51-yocto-standard, but none of the providers
> can be installed
> - conflicting requests
> - nothing provides kernel-module-xeno-can-4.9.51-yocto-standard needed
> by kernel-module-canopen-sync-4.9.51-yocto-standard-git-r0.2.neo_sirius
>
It seems this modules is not built can you check if that’s the case ? You
might look for ipk or rpm in deploy area with this name
>
> ERROR: sirlinux4-image-qt4e-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /workspace/neo-sirius_sirlinux4/build/tmp/work/neo_sirius-poky-linux-gnueabi/sirlinux4-image-qt4e/1.0-r0/temp/log.do_rootfs.9126
> ERROR: Task
> (/workspace/neo-sirius_sirlinux4/meta-sirlinux/recipes-qt4/images/sirlinux4-image-qt4e.bb:do_rootfs)
> failed with exit code '1'
>
>
> I don't understand how exactly the modules dependencies works...
> Initially, I suppose that PROVIDES variable was updated automatically with
> the correct modules names when compiled like module from kernel but now, I
> don't know if I have to specify it manually or is there any other way?
>
> Regards,
> Matteo
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
[-- Attachment #2: Type: text/html, Size: 2476 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: in-tree module dependency
2019-09-04 13:54 ` Khem Raj
@ 2019-09-04 14:10 ` Matteo Facchinetti
2019-09-04 14:22 ` Khem Raj
0 siblings, 1 reply; 6+ messages in thread
From: Matteo Facchinetti @ 2019-09-04 14:10 UTC (permalink / raw)
To: Khem Raj; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]
Il giorno mer 4 set 2019 alle ore 15:54 Khem Raj <raj.khem@gmail.com> ha
scritto:
>
>
> On Wed, Sep 4, 2019 at 2:58 AM Matteo Facchinetti <
> matteo.facchinetti@sirius-es.it> wrote:
>
>> Hi,
>>
>> I have a problem with a custom kernel module's recipe that depends to an
>> other module (in-tree).
>> My kernel module recipes built seems OK, but I have a problem when doing
>> the rootfs image stage.
>>
>> Error:
>> Problem: package packagegroup-console-sirlinux-1.0-r0.0.noarch requires
>> canopen-sync, but none of the providers can be installed
>> - package canopen-sync-git-r0.2.neo_sirius requires
>> kernel-module-canopen-sync-4.9.51-yocto-standard, but none of the providers
>> can be installed
>> - conflicting requests
>> - nothing provides kernel-module-xeno-can-4.9.51-yocto-standard needed
>> by kernel-module-canopen-sync-4.9.51-yocto-standard-git-r0.2.neo_sirius
>>
>
> It seems this modules is not built can you check if that’s the case ? You
> might look for ipk or rpm in deploy area with this name
>
I have checked and module is built.
In build/tmp/deploy/rpm/neo_sirius there's this file:
kernel-module-xeno-can-4.9.51+ipipe+git0+0774eacea2_089d772038-r0.1.neo_sirius.rpm
>
>> ERROR: sirlinux4-image-qt4e-1.0-r0 do_rootfs: Function failed: do_rootfs
>> ERROR: Logfile of failure stored in:
>> /workspace/neo-sirius_sirlinux4/build/tmp/work/neo_sirius-poky-linux-gnueabi/sirlinux4-image-qt4e/1.0-r0/temp/log.do_rootfs.9126
>> ERROR: Task
>> (/workspace/neo-sirius_sirlinux4/meta-sirlinux/recipes-qt4/images/sirlinux4-image-qt4e.bb:do_rootfs)
>> failed with exit code '1'
>>
>>
>> I don't understand how exactly the modules dependencies works...
>> Initially, I suppose that PROVIDES variable was updated automatically
>> with the correct modules names when compiled like module from kernel but
>> now, I don't know if I have to specify it manually or is there any other
>> way?
>>
>> Regards,
>> Matteo
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
[-- Attachment #2: Type: text/html, Size: 3405 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: in-tree module dependency
2019-09-04 14:10 ` Matteo Facchinetti
@ 2019-09-04 14:22 ` Khem Raj
2019-09-04 16:41 ` Matteo Facchinetti
0 siblings, 1 reply; 6+ messages in thread
From: Khem Raj @ 2019-09-04 14:22 UTC (permalink / raw)
To: Matteo Facchinetti; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 2392 bytes --]
On Wed, Sep 4, 2019 at 7:10 AM Matteo Facchinetti <
matteo.facchinetti@sirius-es.it> wrote:
>
>
> Il giorno mer 4 set 2019 alle ore 15:54 Khem Raj <raj.khem@gmail.com> ha
> scritto:
>
>>
>>
>> On Wed, Sep 4, 2019 at 2:58 AM Matteo Facchinetti <
>> matteo.facchinetti@sirius-es.it> wrote:
>>
>>> Hi,
>>>
>>> I have a problem with a custom kernel module's recipe that depends to an
>>> other module (in-tree).
>>> My kernel module recipes built seems OK, but I have a problem when doing
>>> the rootfs image stage.
>>>
>>> Error:
>>> Problem: package packagegroup-console-sirlinux-1.0-r0.0.noarch requires
>>> canopen-sync, but none of the providers can be installed
>>> - package canopen-sync-git-r0.2.neo_sirius requires
>>> kernel-module-canopen-sync-4.9.51-yocto-standard, but none of the providers
>>> can be installed
>>> - conflicting requests
>>> - nothing provides kernel-module-xeno-can-4.9.51-yocto-standard needed
>>> by kernel-module-canopen-sync-4.9.51-yocto-standard-git-r0.2.neo_sirius
>>>
>>
>> It seems this modules is not built can you check if that’s the case ? You
>> might look for ipk or rpm in deploy area with this name
>>
>
> I have checked and module is built.
> In build/tmp/deploy/rpm/neo_sirius there's this file:
>
> kernel-module-xeno-can-4.9.51+ipipe+git0+0774eacea2_089d772038-r0.1.neo_sirius.rpm
>
This has different version than what dep is asking for
>
>
>
>>
>>> ERROR: sirlinux4-image-qt4e-1.0-r0 do_rootfs: Function failed: do_rootfs
>>> ERROR: Logfile of failure stored in:
>>> /workspace/neo-sirius_sirlinux4/build/tmp/work/neo_sirius-poky-linux-gnueabi/sirlinux4-image-qt4e/1.0-r0/temp/log.do_rootfs.9126
>>> ERROR: Task
>>> (/workspace/neo-sirius_sirlinux4/meta-sirlinux/recipes-qt4/images/sirlinux4-image-qt4e.bb:do_rootfs)
>>> failed with exit code '1'
>>>
>>>
>>> I don't understand how exactly the modules dependencies works...
>>> Initially, I suppose that PROVIDES variable was updated automatically
>>> with the correct modules names when compiled like module from kernel but
>>> now, I don't know if I have to specify it manually or is there any other
>>> way?
>>>
>>> Regards,
>>> Matteo
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
[-- Attachment #2: Type: text/html, Size: 4124 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: in-tree module dependency
2019-09-04 14:22 ` Khem Raj
@ 2019-09-04 16:41 ` Matteo Facchinetti
2019-09-05 12:53 ` Matteo Facchinetti
0 siblings, 1 reply; 6+ messages in thread
From: Matteo Facchinetti @ 2019-09-04 16:41 UTC (permalink / raw)
To: Khem Raj; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]
Il giorno mer 4 set 2019 alle ore 16:23 Khem Raj <raj.khem@gmail.com> ha
scritto:
>
>
> On Wed, Sep 4, 2019 at 7:10 AM Matteo Facchinetti <
> matteo.facchinetti@sirius-es.it> wrote:
>
>>
>>
>> Il giorno mer 4 set 2019 alle ore 15:54 Khem Raj <raj.khem@gmail.com> ha
>> scritto:
>>
>>>
>>>
>>> On Wed, Sep 4, 2019 at 2:58 AM Matteo Facchinetti <
>>> matteo.facchinetti@sirius-es.it> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have a problem with a custom kernel module's recipe that depends to
>>>> an other module (in-tree).
>>>> My kernel module recipes built seems OK, but I have a problem when
>>>> doing the rootfs image stage.
>>>>
>>>> Error:
>>>> Problem: package packagegroup-console-sirlinux-1.0-r0.0.noarch
>>>> requires canopen-sync, but none of the providers can be installed
>>>> - package canopen-sync-git-r0.2.neo_sirius requires
>>>> kernel-module-canopen-sync-4.9.51-yocto-standard, but none of the providers
>>>> can be installed
>>>> - conflicting requests
>>>> - nothing provides kernel-module-xeno-can-4.9.51-yocto-standard
>>>> needed by
>>>> kernel-module-canopen-sync-4.9.51-yocto-standard-git-r0.2.neo_sirius
>>>>
>>>
>>> It seems this modules is not built can you check if that’s the case ?
>>> You might look for ipk or rpm in deploy area with this name
>>>
>>
>> I have checked and module is built.
>> In build/tmp/deploy/rpm/neo_sirius there's this file:
>>
>> kernel-module-xeno-can-4.9.51+ipipe+git0+0774eacea2_089d772038-r0.1.neo_sirius.rpm
>>
>
> This has different version than what dep is asking for
>
Do you mean for subversion at the end (r0.1 / r0.2) or for the filename?
>
>>
>>
>>>
>>>> ERROR: sirlinux4-image-qt4e-1.0-r0 do_rootfs: Function failed: do_rootfs
>>>> ERROR: Logfile of failure stored in:
>>>> /workspace/neo-sirius_sirlinux4/build/tmp/work/neo_sirius-poky-linux-gnueabi/sirlinux4-image-qt4e/1.0-r0/temp/log.do_rootfs.9126
>>>> ERROR: Task
>>>> (/workspace/neo-sirius_sirlinux4/meta-sirlinux/recipes-qt4/images/sirlinux4-image-qt4e.bb:do_rootfs)
>>>> failed with exit code '1'
>>>>
>>>>
>>>> I don't understand how exactly the modules dependencies works...
>>>> Initially, I suppose that PROVIDES variable was updated automatically
>>>> with the correct modules names when compiled like module from kernel but
>>>> now, I don't know if I have to specify it manually or is there any other
>>>> way?
>>>>
>>>> Regards,
>>>> Matteo
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>
[-- Attachment #2: Type: text/html, Size: 4923 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: in-tree module dependency
2019-09-04 16:41 ` Matteo Facchinetti
@ 2019-09-05 12:53 ` Matteo Facchinetti
0 siblings, 0 replies; 6+ messages in thread
From: Matteo Facchinetti @ 2019-09-05 12:53 UTC (permalink / raw)
To: Khem Raj; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 3583 bytes --]
Il giorno mer 4 set 2019 alle ore 18:41 Matteo Facchinetti <
matteo.facchinetti@sirius-es.it> ha scritto:
>
>
> Il giorno mer 4 set 2019 alle ore 16:23 Khem Raj <raj.khem@gmail.com> ha
> scritto:
>
>>
>>
>> On Wed, Sep 4, 2019 at 7:10 AM Matteo Facchinetti <
>> matteo.facchinetti@sirius-es.it> wrote:
>>
>>>
>>>
>>> Il giorno mer 4 set 2019 alle ore 15:54 Khem Raj <raj.khem@gmail.com>
>>> ha scritto:
>>>
>>>>
>>>>
>>>> On Wed, Sep 4, 2019 at 2:58 AM Matteo Facchinetti <
>>>> matteo.facchinetti@sirius-es.it> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have a problem with a custom kernel module's recipe that depends to
>>>>> an other module (in-tree).
>>>>> My kernel module recipes built seems OK, but I have a problem when
>>>>> doing the rootfs image stage.
>>>>>
>>>>> Error:
>>>>> Problem: package packagegroup-console-sirlinux-1.0-r0.0.noarch
>>>>> requires canopen-sync, but none of the providers can be installed
>>>>> - package canopen-sync-git-r0.2.neo_sirius requires
>>>>> kernel-module-canopen-sync-4.9.51-yocto-standard, but none of the providers
>>>>> can be installed
>>>>> - conflicting requests
>>>>> - nothing provides kernel-module-xeno-can-4.9.51-yocto-standard
>>>>> needed by
>>>>> kernel-module-canopen-sync-4.9.51-yocto-standard-git-r0.2.neo_sirius
>>>>>
>>>>
>>>> It seems this modules is not built can you check if that’s the case ?
>>>> You might look for ipk or rpm in deploy area with this name
>>>>
>>>
>>> I have checked and module is built.
>>> In build/tmp/deploy/rpm/neo_sirius there's this file:
>>>
>>> kernel-module-xeno-can-4.9.51+ipipe+git0+0774eacea2_089d772038-r0.1.neo_sirius.rpm
>>>
>>
>> This has different version than what dep is asking for
>>
>
> Do you mean for subversion at the end (r0.1 / r0.2) or for the filename?
>
>
Ahh... OK now I understand. (PV)
In my kernel recipe there was setted:
LINUX_VERSION = 4.9.51-ipipe
PV = "${LINUX_VERSION}+git${SRCPV}"
KERNEL_MODULE_PACKAGE_SUFFIX = ""
With this config, yocto generate the follow PV on package filename:
-4.9.51+ipipe+git0+0774eacea2_089d772038
but all references in the relative RPM .spec file were wrong:
-4.9.51-yocto-standard
I believe it dangerours because image build works properly until you add a
recipes that have a kernel module as dependecy.
To solve this problem, I've deleted
KERNEL_MODULE_PACKAGE_SUFFIX = ""
I've changed to
LINUX_VERSION = 4.9
PV = 4.9.51
and I've added
LINUX_VERSION_EXTENSION = "-mainline-xenomai"
Regards,
Matteo
>
>>
>>>
>>>
>>>>
>>>>> ERROR: sirlinux4-image-qt4e-1.0-r0 do_rootfs: Function failed:
>>>>> do_rootfs
>>>>> ERROR: Logfile of failure stored in:
>>>>> /workspace/neo-sirius_sirlinux4/build/tmp/work/neo_sirius-poky-linux-gnueabi/sirlinux4-image-qt4e/1.0-r0/temp/log.do_rootfs.9126
>>>>> ERROR: Task
>>>>> (/workspace/neo-sirius_sirlinux4/meta-sirlinux/recipes-qt4/images/sirlinux4-image-qt4e.bb:do_rootfs)
>>>>> failed with exit code '1'
>>>>>
>>>>>
>>>>> I don't understand how exactly the modules dependencies works...
>>>>> Initially, I suppose that PROVIDES variable was updated automatically
>>>>> with the correct modules names when compiled like module from kernel but
>>>>> now, I don't know if I have to specify it manually or is there any other
>>>>> way?
>>>>>
>>>>> Regards,
>>>>> Matteo
>>>>>
>>>>> --
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto@yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>
>>>>
[-- Attachment #2: Type: text/html, Size: 6497 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-09-05 12:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-04 9:56 in-tree module dependency Matteo Facchinetti
2019-09-04 13:54 ` Khem Raj
2019-09-04 14:10 ` Matteo Facchinetti
2019-09-04 14:22 ` Khem Raj
2019-09-04 16:41 ` Matteo Facchinetti
2019-09-05 12:53 ` Matteo Facchinetti
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.