qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Bochnig, Martin" <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc?
Date: Sun, 29 Aug 2004 16:53:07 +0200	[thread overview]
Message-ID: <4131EDD3.4050502@gmx.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408291631020.17963@wgmdd8.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

>>gmake[1]: warning:  Clock skew detected.  Your build may be incomplete.
> 
> 
> This means that the file change times are not as they are supposed to be.
> Are you working on the same files from two different machines? Something
> like NFS mounted root, and trying to compile from one machine continuing
> on the other?
Yes, from 5 different hosts.
But I use to do a "gmake distclean" every time.
I change the "share -F nfs -o rw,root=192.168.0.[n] [DirToExport]" too.

Don't know.
> 

> This means that at least the configure script's output has an incorrect
> time set.
Interesting - I currently don't run NTP and every machine's local date 
differs from each other.
> 
> How about a "make distclean && ./configure && make"?
> 
> I once had a black screen: I was redirecting the X DISPLAY to an IRIX
> machine. Only with my VNC patch I was able to see that the SDL output was
> somehow wrong, but VNC showed what I expected.
Yes, that's another problem.
I got QEMU 0.6.0 perfectly up and running on my AMD32 Solaris10_60 host.
Everything works, but forwarding to non-XF86 X-Servers or just to 
slightly older XF86 servers makes all my keyboards unusable (mapping 
extremely chaotic == UNusable).
When using the very ltest VNC4.x it works just fine.
I had many hours of trouble due to the lack of appropriate information.
Booting Solaris_x86 guests under Solaris_x86__10_60 HOST still results 
in a very similar error - even when using VNC 4.x as Mini-XF86 server.

Best regards,
Martin


> 
> Ciao,
> Dscho
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 
> 

  reply	other threads:[~2004-08-29 15:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 11:06 [Qemu-devel] sparc? Bochnig, Martin
2004-08-26 22:11 ` Bochnig, Martin
2004-08-27 23:29 ` Bochnig, Martin
2004-08-27 23:34   ` Lennert Buytenhek
2004-08-27 23:58     ` Bochnig, Martin
2004-08-28  0:05       ` Lennert Buytenhek
2004-08-28  0:14         ` Bochnig, Martin
     [not found]   ` <413083B1.2040102@bellard.org>
2004-08-28 16:55     ` Bochnig, Martin
2004-08-29 14:26       ` Bochnig, Martin
2004-08-29 14:37         ` Johannes Schindelin
2004-08-29 14:53           ` Bochnig, Martin [this message]
2004-08-29 15:12           ` Bochnig, Martin
2004-08-31 22:22         ` Richard Zidlicky
  -- strict thread matches above, loose matches on Subject: below --
2004-08-26 10:46 Bochnig, Martin
2004-01-02 16:57 Yelich, Scott D.
2004-01-02 18:16 ` Fabrice Bellard
2004-01-02 20:48   ` NunO fELICIO
2004-01-02 21:49   ` Raymond W. Lucke IV
2004-01-02 23:01     ` Satadru Pramanik

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=4131EDD3.4050502@gmx.com \
    --to=mb1x@gmx.com \
    --cc=bochnig@pool.math.tu-berlin.de \
    --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 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).