From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Problem to compile kernel (enable nfsd)
Date: Thu, 30 May 2013 08:31:18 -0400 [thread overview]
Message-ID: <CADkTA4NX7T8GGK2FJtknB4dnxFBOFRdKB-NSVEziUMBtPX4ocw@mail.gmail.com> (raw)
In-Reply-To: <3685099.fniMcpLHSL@helios>
On Thu, May 30, 2013 at 5:03 AM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Wednesday 29 May 2013 23:33:04 Bruce Ashfield wrote:
>> On 13-05-29 3:05 PM, Caio wrote:
>> > bitbake -e -c kernel_configme linux-yocto-custom | grep KERNEL_FEATURES
>> > # $KERNEL_FEATURES [2 operations]
>> > KERNEL_FEATURES="features/nfsd/nfsd-enable.scc"
>>
>> Aha. That's the problem with cutting and pasting patches, I missed this
>> part of the fix:
>>
>> diff --git a/meta/conf/machine/include/qemu.inc
>> b/meta/conf/machine/include/qemu.inc
>> index 7111926..b303191 100644
>> --- a/meta/conf/machine/include/qemu.inc
>> +++ b/meta/conf/machine/include/qemu.inc
>> @@ -25,4 +25,4 @@ PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>> EXTRA_IMAGEDEPENDS += "qemu-native qemu-helper-native"
>>
>> # Provide the nfs server kernel module for all qemu images
>> -KERNEL_FEATURES_append = " features/nfsd/nfsd-enable.scc"
>> +KERNEL_FEATURES-pn_linux-yocto_append = " features/nfsd/nfsd-enable.scc"
>
> I'm afraid this is not correct either.
>
> You need pn- instead of pn_, and I think in terms of ordering you also need
> _append_pn-linux-yocto instead of _pn-linux-yocto_append.
Heh. Well that wasn't the patch, that was me typing it in at 1AM based on
a modified line from the original :) My laptop with the real change decided
to drop of the network.
Bruce
>
> I'd really appreciate the final fix for this as soon as possible so I can
> integrate it into the dylan branch for the 1.4.1 release.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
next prev parent reply other threads:[~2013-05-30 12:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 18:15 Problem to compile kernel (enable nfsd) Caio
2013-05-29 18:19 ` Tom Zanussi
2013-05-29 18:19 ` Bruce Ashfield
2013-05-29 18:22 ` Tom Zanussi
2013-05-29 18:30 ` Caio
2013-05-29 18:34 ` Bruce Ashfield
2013-05-29 18:53 ` Caio
2013-05-29 18:58 ` Bruce Ashfield
2013-05-29 19:05 ` Caio
2013-05-29 19:50 ` Bruce Ashfield
2013-05-30 3:33 ` Bruce Ashfield
2013-05-30 9:03 ` Paul Eggleton
2013-05-30 12:31 ` Bruce Ashfield [this message]
2013-06-03 13:22 ` Caio
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=CADkTA4NX7T8GGK2FJtknB4dnxFBOFRdKB-NSVEziUMBtPX4ocw@mail.gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=paul.eggleton@linux.intel.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.