All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: X O <bexoff@gmail.com>
Cc: kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: qemu fails to build with glibc-2.15
Date: Mon, 16 Jul 2012 18:14:48 +0300	[thread overview]
Message-ID: <50042FE8.1030300@redhat.com> (raw)
In-Reply-To: <CAEy7y0fiwdJsuU69HMhf_FGbVbSy-Fh8c1CXfOioKYEZkF7A7g@mail.gmail.com>

(fixed mailing list)

On 07/16/2012 03:37 PM, X O wrote:
> Hello,
> 
> I suspect upgrading my system to glibc-2.15 was a mistake. It seems to
> be qemu-1.0.1, and latter versions including qemu-1.1.1, can't be
> compiled anymore. Yes, I did search around and that led me to glibc,
> resp. http://sourceware.org/ml/libc-ports/2011-08/msg00019.html
> 
> Please, could somebody confirm or deny the following error is thanks
> to glibc-2.15?
> Is there a way to compile qemu with glibc-2.15?
> Or is my system broken?
> 
> ~~~
>   CC    i386-linux-user/syscall.o
> /tmp/qemu-1.1.1/linux-user/syscall.c: In function 'sys_getdents':
> /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: error: '__NR_getdents'
> undeclared (first use in this function)
> /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: note: each undeclared
> identifier is reported only once for each function it appears in
> /tmp/qemu-1.1.1/linux-user/syscall.c: In function '_llseek':
> /tmp/qemu-1.1.1/linux-user/syscall.c:224:1: error: '__NR_lseek'
> undeclared (first use in this function)

Please report the output of

  grep -r __NR_getdents /usr/include/

on your system.



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



WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: X O <bexoff@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] qemu fails to build with glibc-2.15
Date: Mon, 16 Jul 2012 18:14:48 +0300	[thread overview]
Message-ID: <50042FE8.1030300@redhat.com> (raw)
In-Reply-To: <CAEy7y0fiwdJsuU69HMhf_FGbVbSy-Fh8c1CXfOioKYEZkF7A7g@mail.gmail.com>

(fixed mailing list)

On 07/16/2012 03:37 PM, X O wrote:
> Hello,
> 
> I suspect upgrading my system to glibc-2.15 was a mistake. It seems to
> be qemu-1.0.1, and latter versions including qemu-1.1.1, can't be
> compiled anymore. Yes, I did search around and that led me to glibc,
> resp. http://sourceware.org/ml/libc-ports/2011-08/msg00019.html
> 
> Please, could somebody confirm or deny the following error is thanks
> to glibc-2.15?
> Is there a way to compile qemu with glibc-2.15?
> Or is my system broken?
> 
> ~~~
>   CC    i386-linux-user/syscall.o
> /tmp/qemu-1.1.1/linux-user/syscall.c: In function 'sys_getdents':
> /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: error: '__NR_getdents'
> undeclared (first use in this function)
> /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: note: each undeclared
> identifier is reported only once for each function it appears in
> /tmp/qemu-1.1.1/linux-user/syscall.c: In function '_llseek':
> /tmp/qemu-1.1.1/linux-user/syscall.c:224:1: error: '__NR_lseek'
> undeclared (first use in this function)

Please report the output of

  grep -r __NR_getdents /usr/include/

on your system.



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

  parent reply	other threads:[~2012-07-16 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 12:37 qemu fails to build with glibc-2.15 X O
2012-07-16 14:11 ` Veruca Salt
2012-07-16 14:56   ` X O
2012-07-16 15:14 ` Avi Kivity [this message]
2012-07-16 15:14   ` [Qemu-devel] " Avi Kivity
2012-07-16 16:35   ` X O
2012-07-16 16:35     ` [Qemu-devel] " X O
2012-07-17  9:38     ` X O
2012-07-17  9:38       ` [Qemu-devel] " X O
2012-07-17  9:51       ` Peter Maydell
2012-07-17  9:51         ` Peter Maydell
2012-07-17 10:01         ` X O
2012-07-17 10:01           ` X O
2012-07-21 11:34 ` X O
2012-07-21 11:34   ` [Qemu-devel] " X O

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=50042FE8.1030300@redhat.com \
    --to=avi@redhat.com \
    --cc=bexoff@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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.