All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Nigel Horne <njh@bandsman.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mips guest
Date: Wed, 19 Sep 2007 13:53:21 +0100	[thread overview]
Message-ID: <20070919125321.GP9972@networkno.de> (raw)
In-Reply-To: <46F1180C.6050905@bandsman.co.uk>

Nigel Horne wrote:
> I suddenly remembered I'd forgotten to do a "make clean" after my last 
> checkout (oops).
>
> So I did that, and got this compilation error:
>
> ...
> In file included from /home/njh/src/qemu/linux-user/syscall.c:4040:
> /home/njh/src/qemu/linux-user/syscall.c: In function `do_syscall':
> /usr/include/bits/unistd.h:62: sorry, unimplemented: inlining failed in 
> call to 'pread': recursive inlining
> /home/njh/src/qemu/linux-user/syscall.c:63: sorry, unimplemented: called 
> from here
> make[1]: *** [syscall.o] Error 1
> make[1]: Leaving directory `/home/njh/src/qemu/i386-linux-user'
> make: *** [subdir-i386-linux-user] Error 2
>
> This is because both unistd.h and linux/unistd.h are included. Remove 
> unistd.h from line 27 and that compiles OK.

I don't see this on my systems. It looks like broken kernel headers.
What host (OS version) do you use?


Thiemo

  reply	other threads:[~2007-09-19 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  9:21 [Qemu-devel] Mips guest Nigel Horne
2007-09-19  9:43 ` Johannes Schindelin
2007-09-19 12:37   ` Nigel Horne
2007-09-19 12:53     ` Thiemo Seufer [this message]
2007-09-19 13:49       ` Nigel Horne
2007-09-19 14:33         ` Ronald
2007-09-19 15:07           ` Nigel Horne
2007-09-19 10:16 ` Thiemo Seufer

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=20070919125321.GP9972@networkno.de \
    --to=ths@networkno.de \
    --cc=njh@bandsman.co.uk \
    --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.