public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Michael Park <emparq@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: 'make' is no longer producing *.ko files?
Date: Wed, 31 Dec 2008 12:15:59 +0200	[thread overview]
Message-ID: <495B465F.5090702@redhat.com> (raw)
In-Reply-To: <50ebac890812301325o40fb1c01q3329c1f91084fd5e@mail.gmail.com>

Michael Park wrote:
> Hello,
>
> I'm running into a strange problem of 'make' not producing any *.ko
> files recently (kvm-82). This seems rather odd, as 'make' still
> completes successfully (echo $? returns 0), and there are *.o files
> that are output as a result.
>
> I've done a paste of my ./configure and make steps here:
>
> http://rafb.net/p/BKK6yH11.html
>
> [emparq@bart:~]$ uname -a
> Linux bart.localdomain 2.6.27.9-73.fc9.x86_64 #1 SMP Tue Dec 16
> 14:54:03 EST 2008x86_64 x86_64 x86_64 GNU/Linux
> [emparq@bart:~]$ cat /etc/issue
> Fedora release 9 (Sulphur)
> Kernel \r on an \m (\l)
>
> Has anyone seen this behavior before? (I successfully compiled kvm-79,
> kvm-80, and kvm-81, however recently I've noticed that this problem is
> occurring when I try to build those previous kvm releases as well. Is
> this a Fedora kernel-devel problem?
>
>   

Very strange. Can you add 'V=1' to the line that starts with $(MAKE) -C 
$(KERNELDIR) in kernel/Makefile and rerun? post the log.


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-12-31 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 21:25 'make' is no longer producing *.ko files? Michael Park
2008-12-31  0:16 ` walt
2008-12-31  1:15   ` Michael Park
2008-12-31  1:34     ` walt
2008-12-31 10:15 ` Avi Kivity [this message]
     [not found]   ` <50ebac890901022112x5834970x4d46e77cef2e7e2c@mail.gmail.com>
2009-01-04 12:57     ` Avi Kivity

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=495B465F.5090702@redhat.com \
    --to=avi@redhat.com \
    --cc=emparq@gmail.com \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox