On 7/26/21 8:48 AM, Rasmus Villemoes wrote:
Looking at log.do_rootfs, it seems that opkg gets invoked in exactly the
same way with and without the RRECOMMENDS in play:
With RRECOMMENDS, where the build succeeds:
NOTE: Installing the following packages: [...] glib-2.0 iproute2
kernel-image
On 06/07/2021 21.39, Alex Stewart wrote:
> Hey Rasmus,
>
> Sorry for the delay; I was OOO for the holidays and I'm just now working
> through my inbox.
No need to apologize; as it happens I've just now returned from vacation.
> On 6/28/21 4:17 AM, Rasmus Villemoes wrote:
>> On 25/06/2021 18.13,
On 7/6/21 3:12 PM, Richard Purdie wrote:
Kernel modules can be:
a) not built at all
b) built into the kernel3
c) built as separate packages
For OE, where something needs a kernel module, we suggest people:
RRECOMMEND_XXX += "kernel-module-xxx"
and the kernel recipe has PACKAGES_DYNAMIC =
On Tue, 2021-07-06 at 14:39 -0500, Alex Stewart wrote:
> Hey Rasmus,
>
> Sorry for the delay; I was OOO for the holidays and I'm just now working
> through my inbox.
>
> On 6/28/21 4:17 AM, Rasmus Villemoes wrote:
> > On 25/06/2021 18.13, Richard Purdie wrote:
> > > That is probably a bug that
Hey Rasmus,
Sorry for the delay; I was OOO for the holidays and I'm just now working
through my inbox.
On 6/28/21 4:17 AM, Rasmus Villemoes wrote:
On 25/06/2021 18.13, Richard Purdie wrote:
That is probably a bug that needs opening against opkg in bugzilla then.
Added Alex to Cc: (opkg
On Mon, 2021-06-28 at 11:17 +0200, Rasmus Villemoes wrote:
> On 25/06/2021 18.13, Richard Purdie wrote:
> > On Fri, 2021-06-25 at 17:45 +0200, Rasmus Villemoes wrote:
> > > On 25/06/2021 14.16, Richard Purdie wrote:
> > > > On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
> > > >
On 25/06/2021 18.13, Richard Purdie wrote:
> On Fri, 2021-06-25 at 17:45 +0200, Rasmus Villemoes wrote:
>> On 25/06/2021 14.16, Richard Purdie wrote:
>>> On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
>>> lists.openembedded.org wrote:
I noticed that if I have an image recipe that
On Fri, 2021-06-25 at 17:45 +0200, Rasmus Villemoes wrote:
> On 25/06/2021 14.16, Richard Purdie wrote:
> > On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
> > lists.openembedded.org wrote:
> > > I noticed that if I have an image recipe that says
> > >
> > > IMAGE_INSTALL +=
On 25/06/2021 14.16, Richard Purdie wrote:
> On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
> lists.openembedded.org wrote:
>> I noticed that if I have an image recipe that says
>>
>> IMAGE_INSTALL += "kernel-module-foo"
>>
>> it fails as expected when the kernel hasn't been built with
On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via lists.openembedded.org
wrote:
> I noticed that if I have an image recipe that says
>
> IMAGE_INSTALL += "kernel-module-foo"
>
> it fails as expected when the kernel hasn't been built with CONFIG_FOO=m.
>
> However, if at the same time
I noticed that if I have an image recipe that says
IMAGE_INSTALL += "kernel-module-foo"
it fails as expected when the kernel hasn't been built with CONFIG_FOO=m.
However, if at the same time some other package which happens to get
installed in the same image says
RRECOMMENDS_${PN} +=
11 matches
Mail list logo
