all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Rutger Helling <rhelling@mykolab.com>, 34824@debbugs.gnu.org
Subject: [bug#34824] [PATCH staging] libdrm/Mesa Meson patch series
Date: Sun, 17 Mar 2019 19:01:59 +0100	[thread overview]
Message-ID: <87y35d8jmw.fsf@fastmail.com> (raw)
In-Reply-To: <20190312141615.2d96bb7d@mykolab.com>

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Rutger Helling <rhelling@mykolab.com> writes:

> Hey Guix,
>
> this patch series changes libdrm and Mesa to use Meson.
>
> A few notes to go along with the patches:
>
> Patch #1: Libdrm on Github mentions that Autotools is the legacy build
> system for libdrm, so it seems better to change this to use Meson.
> Patch #2: Mesa is gonna drop support for Autotools entirely at some
> point in 2019, so it seems good to make the switch sooner rather than
> later. I think I converted all the configure flags to the new format.
> Patches #3-6: For some reason these packages now need an explicit mesa
> input. I haven't run into other packages that have this problem yet.

The first two patches LGTM, but we should figure out why some packages
need special attention and squash the fixes with the Mesa (or libdrm)
change.

I see the other packages are SDL-related, maybe the libSDL pkg-config
files are different after this change?  Or "sdl-config" prints something
weird?

Thanks for looking after these packages :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-03-17 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 13:16 [bug#34824] [PATCH staging] libdrm/Mesa Meson patch series Rutger Helling
2019-03-17 18:01 ` Marius Bakke [this message]
2019-03-18  9:44   ` Rutger Helling
2019-03-18 14:17     ` Marius Bakke
2019-03-18 15:25       ` Rutger Helling
2019-03-18 16:50         ` Marius Bakke
2019-03-19 10:10           ` bug#34824: " Rutger Helling

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=87y35d8jmw.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=34824@debbugs.gnu.org \
    --cc=rhelling@mykolab.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.