Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mesa3d: override dri path
Date: Sun, 13 Jan 2019 14:11:32 +0100	[thread overview]
Message-ID: <20190113141132.5af03184@windsurf.home> (raw)
In-Reply-To: <20190112190743.7780-1-romain.naour@gmail.com>

Hello,

On Sat, 12 Jan 2019 20:07:43 +0100, Romain Naour wrote:
> Since the bump to 1.5.3, pkgconf prepends the sysroot to all absolute
> paths found in the .pc file.

No, this is not what pkgconf is doing. pkg-config is prepending the
sysroot only to:

 includedir
 libdir
 mapdir
 pkgdatadir
 sdkdir

However, since dridriverdir is defined in the .pc file as being equal
to ${libdir}/dri, it inherits from the sysroot-prefixed libdir path.

I'll fix this up in the commit log when applying.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-01-13 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12 19:07 [Buildroot] [PATCH] package/mesa3d: override dri path Romain Naour
2019-01-13 13:11 ` Thomas Petazzoni [this message]
2019-01-14 21:31 ` Thomas Petazzoni

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=20190113141132.5af03184@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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