All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: "raj.khem@gmail.com >> Khem Raj" <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: New kernel error after syncing
Date: Mon, 25 Aug 2014 15:56:57 -0700	[thread overview]
Message-ID: <53FBBF39.7010909@gmail.com> (raw)
In-Reply-To: <CADkTA4PeNvAuv8SDfUNtpsTT_25OHvTMRbuFtAe2-gJZQxB4rA@mail.gmail.com>

Khem

it was the config option not being set..

seems like a kernel bug to me.. kconfig or otherwise.

thanks for the help.
- Armin

On 08/24/2014 05:14 PM, Bruce Ashfield wrote:
> On Sun, Aug 24, 2014 at 7:02 PM, akuster808 <akuster808@gmail.com> wrote:
>>
>> Hello,
>>
>> Is anyone else seeing kernel build issue on 3.14 with the resent updates?
>>
>>
>> I am getting the following errors on ppc64 (standard/qemuppc). x86-64 built
>> fine (core-image-minimal). building ppc now.
>
> Hopefully qemuppc is building 32 bit :) .. but outside of that, I was
> able to build 3.14
> fine on Friday.  But I just started another build to see if something
> snuck past in the
> recent feature merges.
>
> Bruce
>
>>
>> |   LD      init/built-in.o
>> | mm/built-in.o: In function `.vm_cgroup_css_alloc':
>> | vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
>> | vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
>> | mm/built-in.o: In function `.vm_cgroup_read_u64':
>> | vm_cgroup.c:(.text+0x711c4): undefined reference to
>> `.res_counter_read_u64'
>> | mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
>> | (.text+0x71348): undefined reference to `.res_counter_charge'
>> | mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
>> | (.text+0x713a0): undefined reference to `.res_counter_uncharge'
>> | mm/built-in.o: In function `.vm_cgroup_charge_shmem':
>> | (.text+0x71508): undefined reference to `.res_counter_charge'
>> | mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
>> | (.text+0x71560): undefined reference to `.res_counter_uncharge'
>> | make[2]: *** [vmlinux] Error 1
>> | make[1]: *** [sub-make] Error 2
>> | make: *** [all] Error 2
>>
>> - armin
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>


  reply	other threads:[~2014-08-25 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 23:02 New kernel error after syncing akuster808
2014-08-24 23:22 ` Khem Raj
2014-08-24 23:24   ` Khem Raj
2014-08-25  0:14 ` Bruce Ashfield
2014-08-25 22:56   ` akuster808 [this message]
2014-08-25 23:30     ` Khem Raj
2014-08-26  4:11       ` Bruce Ashfield

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=53FBBF39.7010909@gmail.com \
    --to=akuster808@gmail.com \
    --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.