All of lore.kernel.org
 help / color / mirror / Atom feed
From: Struan Bartlett <struan@praguespringpeople.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Current state of RFB patch
Date: Mon, 21 Mar 2005 21:59:41 +0100	[thread overview]
Message-ID: <423F35BD.1050305@praguespringpeople.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0503212044360.10588@wgmdd8.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

>On Mon, 21 Mar 2005, zitu wrote:
>  
>
>>Quoting Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>>    
>>
>>>I wanted to make a new patch this year with an updated mouse handling, but
>>>I didn't come around to do it yet. I'm not at my development machine ATM,
>>>but tomorrow I will create an RFB10 patch, promise!
>>>      
>>>
>Well, here you are:
>
>http://libvncserver.sf.net/qemu/qemu-rfb10.patch.gz
>  
>
This patches, but compile breaks:

gcc-3.3 -march=pentium -DQEMU_TOOL -Wall -O2 -g -fno-strict-aliasing -g 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o qemu-img 
qemu-img.c block.c block-cow.c block-qcow.c aes.c block-vmdk.c 
block-cloop.c block-dmg.c -lz
sh create_keysym_header.sh vnc ""
Usage: create_keysym_header.sh vnc|sdl cflags
make: *** [keysym_adapter_vnc.h] Error 1

Looks like create_keysym_header.sh isn't being called with a second 
argument that gets past it's argument checking. Strange because my 
config-host.mak has CFLAGS=-O2 in it. Anyway, hacking 
create_keysym_header.sh to hardcode cflags=-O2 allowed my compile to 
continue. But now I'm having a problem launching QEMU with -vnc.

$ qemu -hda win2k.qcow -m 64  -monitor stdio -k en-gb -vnc
<snip>
Warning: could not read keymap - falling back native keycodes!
Could not initialize keyboard

The keymap files are there alright in /usr/local/share/qemu/keymaps/ and 
the same command, minus the -vnc, starts QEMU just fine.

Any suggestions?

Struan

  parent reply	other threads:[~2005-03-21 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 18:43 [Qemu-devel] Current state of RFB patch Andreas Bollhalder
2005-03-20 21:55 ` Johannes Schindelin
2005-03-21 13:15   ` zitu
2005-03-21 19:50     ` Johannes Schindelin
2005-03-21 20:14       ` use.reply-to.address
2005-03-21 20:26         ` Jim C. Brown
2005-03-21 20:59       ` Struan Bartlett [this message]
2005-03-22  1:13         ` Johannes Schindelin
2005-04-01 16:45           ` Andreas Bollhalder
2005-03-22  6:46       ` Brad Campbell
2005-03-22 11:53       ` Andreas Bollhalder
2005-03-22  8:15     ` zitu

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=423F35BD.1050305@praguespringpeople.org \
    --to=struan@praguespringpeople.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.