qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Dustin Kirkland <kirkland@canonical.com>
Subject: Re: [Qemu-devel] [PATCH][RFC] Fix SDL on evdev hosts
Date: Mon, 09 Mar 2009 20:51:50 -0500	[thread overview]
Message-ID: <49B5C7B6.9080407@codemonkey.ws> (raw)
In-Reply-To: <Pine.LNX.4.64.0903100150150.2346@linmac.oyster.ru>

malc wrote:
>> +
>>  ##########################################
>>  # VNC TLS detection
>>  if test "$vnc_tls" = "yes" ; then
>> @@ -1393,6 +1409,8 @@ if test "$sdl1" = "yes" ; then
>>    echo "CONFIG_SDL=yes" >> $config_mak
>>    if test "$target_softmmu" = "no" -o "$static" = "yes"; then
>>      echo "SDL_LIBS=$sdl_static_libs" >> $config_mak
>> +  elif test "$sdl_x11" = "yes" ; then
>> +    echo "SDL_LIBS=`$sdl_config --libs` -lX11" >> $config_mak
>>     
>                                            ^^^^^ this broke the
> build over here, X11 on this box with this installation of OS and
> X puts libX11 into /usr/X11R6/lib.
>   

This is a non-Linux unix, right?  Is the X install actually xfree86?

We can either add the -lX11 flag to the build test which would 
effectively disable this code on your system or we could add a hard 
coded /usr/X11R6/lib to the search path.  In general, I don't know of a 
way to detect the location of X11 :-/

If it's not xfree86 though, the code probably isn't useful anyway in 
which case, we can just disable it.

Regards,

Anthony Liguori

> [..snip..]
>
>   

  reply	other threads:[~2009-03-10  1:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 17:34 [Qemu-devel] [PATCH][RFC] Fix SDL on evdev hosts Anthony Liguori
2009-02-27 20:10 ` Blue Swirl
2009-02-27 20:11   ` Anthony Liguori
2009-02-27 21:53   ` malc
2009-03-09 22:53 ` malc
2009-03-10  1:51   ` Anthony Liguori [this message]
2009-03-10 19:16     ` malc

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=49B5C7B6.9080407@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=kirkland@canonical.com \
    --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).