Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d-headers: fix logic to generate the dri.pc file
Date: Fri, 24 Aug 2018 10:20:03 +0200	[thread overview]
Message-ID: <87sh34kwgc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180810214632.21735-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Fri, 10 Aug 2018 23:46:32 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > As noted by Arnout in [1], the logic in mesa3d-headers.mk generates a
 > bogus dri.pc file, which looks like this:

 > prefix=/usr
 > exec_prefix=/usr
 > libdir=/lib
 > includedir=/include
 > dridriverdir=/dri

 > Indeed, the ${...} are expanded as shell variables when the sed
 > command is executed, while the intention is that those ${...} should
 > go in the .pc file. By escaping those using $${...}, we get the
 > expected .pc file:

 > prefix=/usr
 > exec_prefix=/usr
 > libdir=${exec_prefix}/lib
 > includedir=${prefix}/include
 > dridriverdir=${libdir}/dri

 > This was detected by the not yet committed check-package improvement
 > from Ricardo that detects bogus ${...} usage to reference make
 > variables.

 > [1] http://lists.busybox.net/pipermail/buildroot/2018-July/225402.html

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2018.02.x and 2018.05.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-08-24  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 21:46 [Buildroot] [PATCH] mesa3d-headers: fix logic to generate the dri.pc file Thomas Petazzoni
2018-08-11  8:33 ` Yann E. MORIN
2018-08-11 10:37 ` Thomas Petazzoni
2018-08-24  8:20 ` Peter Korsgaard [this message]

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=87sh34kwgc.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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