All of lore.kernel.org
 help / color / mirror / Atom feed
From: tmhikaru@gmail.com
To: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [stable] 2.6.34.4 build failure
Date: Sat, 14 Aug 2010 23:44:53 -0400	[thread overview]
Message-ID: <20100815034453.GA29703@roll> (raw)
In-Reply-To: <20100814211043.GC7799@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

On Sat, Aug 14, 2010 at 02:10:43PM -0700, Greg KH wrote:
> On Sat, Aug 14, 2010 at 08:46:21AM +0200, Sven Joachim wrote:
> > 2.6.34.4 failed to build here:
> > 
> > ,----
> > |   CC      arch/x86/kernel/cpu/vmware.o
> > | arch/x86/kernel/cpu/vmware.c: In function 'vmware_get_tsc_khz':
> > | arch/x86/kernel/cpu/vmware.c:66: error: 'preset_lpj' undeclared (first use in this function)
> > | arch/x86/kernel/cpu/vmware.c:66: error: (Each undeclared identifier is reported only once
> > | arch/x86/kernel/cpu/vmware.c:66: error: for each function it appears in.)
> > | arch/x86/kernel/cpu/vmware.c:68: error: 'HZ' undeclared (first use in this function)
> > | make[3]: *** [arch/x86/kernel/cpu/vmware.o] Error 1
> > | make[2]: *** [arch/x86/kernel/cpu] Error 2
> > | make[1]: *** [arch/x86/kernel] Error 2
> > | make: *** [arch/x86] Error 2
> > `----
> > 
> > The .config file follows.
> 
> If you add:
> 	#include <linux/jiffies.h>
> to that file, does it then build?
> 
> Odd that this isn't showing up in the .35 kernel :(
> 
> thanks,
> 
> greg k-h

	I am having an identical build failure. Adding that include line
indeed fixes it for me.

	Tim McGrath

[-- Attachment #2: Type: application/pgp-signature, Size: 482 bytes --]

  reply	other threads:[~2010-08-15  3:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14  6:46 2.6.34.4 build failure Sven Joachim
2010-08-14 21:10 ` [stable] " Greg KH
2010-08-15  3:44   ` tmhikaru [this message]
2010-08-15  6:08   ` Sven Joachim
  -- strict thread matches above, loose matches on Subject: below --
2010-08-14 22:12 Chris Rankin
2010-08-15 22:04 Brian Lindholm

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=20100815034453.GA29703@roll \
    --to=tmhikaru@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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.