mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org,
	Jaswinder Singh Rajput <jaswinderrajput@gmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: build breakage -- paravirt_{alloc,free}_ldt
Date: Mon, 12 Jan 2009 12:24:58 +0100	[thread overview]
Message-ID: <20090112112458.GA19388@elte.hu> (raw)
In-Reply-To: <3f9a31f40901120319l4fac84e4me193fb314bdbbcaa@mail.gmail.com>


* Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:

> On Mon, Jan 12, 2009 at 4:42 PM, Jiri Kosina <jkosina@suse.cz> wrote:
> > On Mon, 12 Jan 2009, Ingo Molnar wrote:
> >
> >> > with Linus' tree (ae04d14015) doesn't build for me with
> >> >
> >> > arch/x86/kernel/ldt.c: In function 'alloc_ldt':
> >> > arch/x86/kernel/ldt.c:55: error: implicit declaration of function 'paravirt_alloc_ldt'
> >> > arch/x86/kernel/ldt.c:79: error: implicit declaration of function 'paravirt_free_ldt'
> >> >
> >> > Config on http://www.jikos.cz/jikos/junk/.config
> >>
> >> hm, it builds fine here with your config. Did .28 build fine for you? The
> >> only change to this file since .28 has been Jaswinder's "423a540: x86:
> >> ldt.c fix style problems".
> >
> > Puzzled. On one system, I still get this build error even after make
> > mrpoper (I use this machine to build kernel routinely, so it certainly
> > didn't happen a few days ago).
> >
> > But I just tried on different system, and there is builds flawlessly. It's
> > gcc 4.3.1 vs 4.3.2. I will check a little bit more.
> >
> 
> I am using gcc 4.3.2
> 
> Please check 'git diff' if by mistake some thing is gone wrong or check 
> 'git log'

That wont show working tree corruption.

Safest is to move away the working tree into a backup directory and check 
out the tree again:

  cd linux
  mkdir ../linux-backup
  mv * ../linux-backup

  git checkout HEAD .

then, if this solves the build problem, do some forensics by looking at:

 diff -rNu ../linux-backup ../linux'

	Ingo

  reply	other threads:[~2009-01-12 11:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 10:23 Jiri Kosina
2009-01-12 10:52 ` Ingo Molnar
2009-01-12 10:57   ` Jaswinder Singh Rajput
2009-01-12 11:08     ` Jaswinder Singh Rajput
2009-01-12 11:17       ` Ingo Molnar
2009-01-12 11:12   ` Jiri Kosina
2009-01-12 11:18     ` Ingo Molnar
2009-01-12 11:35       ` Jiri Kosina
2009-01-12 11:19     ` Jaswinder Singh Rajput
2009-01-12 11:24       ` Ingo Molnar [this message]
2009-01-12 11:36         ` Jaswinder Singh Rajput
2009-01-12 11:39           ` Ingo Molnar
2009-01-12 11:52             ` Jaswinder Singh Rajput

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=20090112112458.GA19388@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=jaswinderlinux@gmail.com \
    --cc=jaswinderrajput@gmail.com \
    --cc=jeremy@goop.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®