qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Robert Reif <reif@earthlink.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Current CVS build errors on RH9
Date: Sun, 16 Sep 2007 22:40:51 +0100	[thread overview]
Message-ID: <20070916214051.GB9972@networkno.de> (raw)
In-Reply-To: <46D97581.3040406@earthlink.net>

Robert Reif wrote:
> It's been a few months since I comipled from source so I
> just tried with current CVS and got these errors on RH9:
>
> /home/wine/qemu/linux-user/syscall.c: In function `sys_tgkill':
> /home/wine/qemu/linux-user/syscall.c:170: `__NR_tgkill' undeclared (first 
> use in this function)
> /home/wine/qemu/linux-user/syscall.c:170: (Each undeclared identifier is 
> reported only once
> /home/wine/qemu/linux-user/syscall.c:170: for each function it appears in.)

It missed some ifdefs to disable use of those syscalls.

> in various subdirectories and:
>
> /home/wine/qemu/vl.c:59:24: linux/hpet.h: No such file or directory
> /home/wine/qemu/vl.c: In function `hpet_start_timer':
> /home/wine/qemu/vl.c:1222: storage size of `info' isn't known
> /home/wine/qemu/vl.c:1230: `HPET_IRQFREQ' undeclared (first use in this 
> function)
> /home/wine/qemu/vl.c:1230: (Each undeclared identifier is reported only 
> once
> /home/wine/qemu/vl.c:1230: for each function it appears in.)
> /home/wine/qemu/vl.c:1239: `HPET_INFO' undeclared (first use in this 
> function)
> /home/wine/qemu/vl.c:1244: `HPET_EPI' undeclared (first use in this 
> function)
> /home/wine/qemu/vl.c:1249: `HPET_IE_ON' undeclared (first use in this 
> function)
> /home/wine/qemu/vl.c:1222: warning: unused variable `info'

Both should be fixed now.


Thiemo

      parent reply	other threads:[~2007-09-16 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-01 14:21 [Qemu-devel] Current CVS build errors on RH9 Robert Reif
2007-09-02  6:52 ` Mulyadi Santosa
2007-09-02 17:18   ` Alexander Voropay
2007-09-16 21:40 ` Thiemo Seufer [this message]

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=20070916214051.GB9972@networkno.de \
    --to=ths@networkno.de \
    --cc=qemu-devel@nongnu.org \
    --cc=reif@earthlink.net \
    /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;
as well as URLs for NNTP newsgroup(s).