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>
Cc: 34824@debbugs.gnu.org
Subject: [bug#34824] [PATCH staging] libdrm/Mesa Meson patch series
Date: Mon, 18 Mar 2019 15:17:27 +0100	[thread overview]
Message-ID: <87r2b48dxk.fsf@fastmail.com> (raw)
In-Reply-To: <20190318104441.2dacc080@mykolab.com>

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

Rutger Helling <rhelling@mykolab.com> writes:

> Hi Marius,
>
> thanks for the review.
>
> So when I rebuilt my entire system a while back with these patches it
> was only those few SDL packages that were affected. Unfortunately I have
> no way of knowing for sure if it won't happen anywhere else, but it
> does seem to be something contained to just SDL(1).
>
> The packages fail with the following error if "mesa" isn't an explicit
> input:
>
> ld: cannot find -lGL
> collect2: error: ld returned 1 exit status
>
> WDYT? Should I go ahead and push these patches or do you have other
> ideas?

Well, we still don't know why -lGL is suddenly there.  Did you inspect
the pkg-config files or sdl-config output to figure out why?

I suspect Mesa should be propagated somewhere, instead of added as an
input in a bunch of places.

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

  reply	other threads:[~2019-03-18 14:30 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
2019-03-18  9:44   ` Rutger Helling
2019-03-18 14:17     ` Marius Bakke [this message]
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=87r2b48dxk.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.