public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Marco Atzeri <marco.atzeri@gmail.com>
Subject: Re: mesa-18.3.1 and missing xxf86vm
Date: Fri, 28 Dec 2018 15:39:00 -0000	[thread overview]
Message-ID: <541e8c77-bdb7-8e50-2802-f08feac5e3dc@dronecode.org.uk> (raw)
In-Reply-To: <d1b403b3-1aec-fb08-ff0c-eedb1416172f@gmail.com>

On 28/12/2018 06:04, Marco Atzeri wrote:
> I was trying to build latest mesa to see if
> solved a wgl problem on my Intel graphics card
>   https://cygwin.com/ml/cygwin/2018-12/msg00222.html
> 
> but I am blocked by
> ------------------------------------------
> Dependency xxf86vm found: NO (tried pkgconfig)
> 
> meson.build:1353:4: ERROR:  Dependency "xxf86vm" not found, tried pkgconfig
> 
> A full log can be found at
> /cygdrive/d/cyg_pub/devel/mesa/mesa-18.3.1-1.x86_64/src/mesa-18.3.1/x86_64-pc-cygwin/meson-logs/meson-log.txt 
> 
> *** ERROR: meson failed
> -------------------------------------------
> 
> any reason to not have the xxf86vm in cygwin ?

Historically, we haven't bothered with xxf86vm because it makes no sense 
to manipulate the video mode of an X server which is hosted by another 
windowing system.

This particular build issue has been fixed upstream, see [1] et. seq.

[1] 
https://lists.freedesktop.org/archives/mesa-dev/2018-December/211720.html


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-12-28 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28 11:14 Marco Atzeri
2018-12-28 15:39 ` Jon Turney [this message]
2018-12-28 17:25   ` Marco Atzeri

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=541e8c77-bdb7-8e50-2802-f08feac5e3dc@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).