Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/luajit: luajit.pc: return the path to host-luajit from the Buildroot package
Date: Sun, 1 May 2016 23:32:14 +0200	[thread overview]
Message-ID: <20160501233214.74ca9bf0@free-electrons.com> (raw)
In-Reply-To: <1462137728-17445-1-git-send-email-romain.naour@gmail.com>

Hello,

On Sun,  1 May 2016 23:22:08 +0200, Romain Naour wrote:
> The luajit.pc file is manually generated in the luajit Makefile, so it give a wrong
> path for host-luajit.
> 
> $ output/host/usr/bin/pkgconf --cflags luajit
> /usr/include/luajit-2.0
> 
> It should be:
> $ output/host/usr/bin/pkgconf --cflags luajit
> [...]output/host/usr/include/luajit-2.0
> 
> Set PREFIX with $(HOST_DIR)/usr and remove DESTDIR since the installation path
> is DPREFIX=$(DESTDIR)$(PREFIX).
> Otherwise the host-luajit is installed to output/host/home/[...]/output/host/usr
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> v2: remove the post install hook and set PREFIX with $(HOST_DIR)/usr (ThomasP)
> ---
>  package/luajit/luajit.mk | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

I've quite significantly rewritten the commit log, and applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-05-01 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 21:22 [Buildroot] [PATCH v2] package/luajit: luajit.pc: return the path to host-luajit from the Buildroot package Romain Naour
2016-05-01 21:32 ` Thomas Petazzoni [this message]
2016-05-02  7:31   ` Romain Naour

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=20160501233214.74ca9bf0@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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