From: "Mike \(mwester\)" <mwester@dls.net>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Need advice on changing kernel.bbclass
Date: Thu, 7 Jun 2007 06:56:43 -0500 [thread overview]
Message-ID: <045401c7a8fa$ea96f300$6e01a8c0@twilight> (raw)
In-Reply-To: 200706070839.52842.openembedded@hrw.one.pl
Build completed, with this suggestion. :( No joy:
Package: kernel-module-binfmt-misc
Version: 2.4.22.l2.3r63-r18.5
Depends: update-modules, kernel-2.4.22-xfs
Section: kernel
The kernel modules built remain firm in their conviction that they depend
upon the kernel, not kernel-image.
Mike (mwester)
----- Original Message -----
From: "Marcin Juszkiewicz" <openembedded@hrw.one.pl>
To: <openembedded-devel@lists.openembedded.org>
Sent: Thursday, June 07, 2007 1:39 AM
Subject: Re: [oe] Need advice on changing kernel.bbclass
>
> RPROVIDES_kernel-2.4.22-xfs = "kernel-image-2.4.22-xfs" should solve your
> problem.
>
> Change was in kernel*.bbclass and it was discussed on this list -
> thread "[oe] RFC: Kernel image packaging" from 14 March this year.
>
> --
> JID: hrw-jabber.org
> OpenEmbedded developer/consultant
>
> change your mind. it's starting to smell.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2007-06-07 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 4:30 Need advice on changing kernel.bbclass Mike (mwester)
2007-06-07 6:39 ` Marcin Juszkiewicz
2007-06-07 11:26 ` Mike (mwester)
2007-06-07 11:56 ` Mike (mwester) [this message]
2007-06-07 12:41 ` Marcin Juszkiewicz
2007-06-07 18:45 ` Richard Purdie
2007-06-07 20:51 ` Mike (mwester)
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='045401c7a8fa$ea96f300$6e01a8c0@twilight' \
--to=mwester@dls.net \
--cc=openembedded-devel@lists.openembedded.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.