From: Matteo Facchinetti <matteo.facchinetti@sirius-es.it>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: in-tree module dependency
Date: Wed, 4 Sep 2019 16:10:47 +0200 [thread overview]
Message-ID: <CAAjAsiyQN28Z8A_YUNh9r3s+zs326_V78ED_BpVuKj24fNMqJw@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1soFzHWLyGS4jcur6mdUL18dkUt0qYnbiwygOosy-f3X2w@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2019-09-04 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-09-04 14:22 ` Khem Raj
2019-09-04 16:41 ` Matteo Facchinetti
2019-09-05 12:53 ` Matteo Facchinetti
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=CAAjAsiyQN28Z8A_YUNh9r3s+zs326_V78ED_BpVuKj24fNMqJw@mail.gmail.com \
--to=matteo.facchinetti@sirius-es.it \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.org \
/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 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.