From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] kernel NOTE messages fix
Date: Wed, 29 Sep 2010 11:18:25 -0700 [thread overview]
Message-ID: <4CA382F1.8040207@mentor.com> (raw)
In-Reply-To: <AANLkTikv8x4xoAD5zPnprHpo9wcWc1hi8FF=5m8mtCi4@mail.gmail.com>
Frans Meulenbroeks wrote:
> Thanks for the feedback and the acks.
> I'll make a formal patch for this and push it with the acks added.
> Maybe this evening otherwise tomorrow (but if someone can't wait so
> long feel free to make the patch (but please let me know on irc, so we
> do not end up duplicating things))
>
> Wrt the kernel-dev route: I didn't try it, as Henning & Petr (and
> maybe also Eric) tried this before.
>
> Tom, I do encounter issues with scripts and strip either. They are
> still on my to-investigate list and are not related to the issue at
> hand, but when building slugos-image for nslu2 I get the messages
> given below. Guess this is the same problem you are facing.
>
> I'm open for hints on how to fix this one.
I think something like:
- Copy sources, cd to dest
- Backup .config
- make mrproper
- Restore .config to destdir
- make ... modules_prep or so (don't have it off-hand, but make help
shows) which gets things valid again for external modules to build.
Problem is that (a) that won't work on 2.4 and (b) I don't know how far
back, off-hand, that make target exists in 2.6.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-29 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 16:39 [RFC] kernel NOTE messages fix Frans Meulenbroeks
2010-09-28 17:04 ` Denys Dmytriyenko
2010-09-28 17:15 ` Roman I Khimov
2010-09-28 20:06 ` Tom Rini
2010-09-28 21:16 ` Petr Štetiar
2010-09-28 21:14 ` Petr Štetiar
2010-09-29 6:34 ` Eric Bénard
2010-09-29 6:46 ` Frans Meulenbroeks
2010-09-29 18:18 ` Tom Rini [this message]
2010-09-29 18:37 ` Denys Dmytriyenko
2010-09-29 20:16 ` Frans Meulenbroeks
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=4CA382F1.8040207@mentor.com \
--to=tom_rini@mentor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox