All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org
Cc: reif@earthlink.net
Subject: Re: [Qemu-devel] Current CVS build errors on RH9
Date: Sun, 02 Sep 2007 13:52:55 +0700	[thread overview]
Message-ID: <46DA5DC7.9010302@softhome.net> (raw)
In-Reply-To: <46D97581.3040406@earthlink.net>

Hi
>
> /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.)
>
>
>
> /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)
Got that messages too when I try to rebuild the CVS version about 3-4 
days ago on my RH9 box. IMHO the reason is: no tg_kill syscall and hpet 
exists on RH 9. However, I successfully build the same CVS version on 
FC2. So, either we need to make the ./configure script detect such 
occassion and put the relevant ifdefs here and there, or we completely 
don't support those old distributions.

Anybody wants to share his/her thoughts about it?

regards,

Mulyadi

  reply	other threads:[~2007-09-02  7:19 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 [this message]
2007-09-02 17:18   ` Alexander Voropay
2007-09-16 21:40 ` 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=46DA5DC7.9010302@softhome.net \
    --to=a_mulyadi@softhome.net \
    --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 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.