All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Haseeb Ashraf <haseeb_ashraf@mentor.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-oe][PATCH 1/2] modify LUA_CPATH_DEFAULT for 64-bit architectures
Date: Thu, 16 Apr 2020 08:50:08 -0700	[thread overview]
Message-ID: <CAMKF1soS6_L4HpzA5WKuJGZLrnqvnq4qcq-zigYfBX0zhS6EpA@mail.gmail.com> (raw)
In-Reply-To: <20200416102923.27122-1-Haseeb_Ashraf@mentor.com>

Can you rebase this change on top of master or master-next

On Thu, Apr 16, 2020 at 3:29 AM Haseeb Ashraf <haseeb_ashraf@mentor.com> wrote:
>
> LUA_CPATH_DEFAULT for *.so files should include
> LUA_ROOT/lib64/lua/LUA_VDIR not LUA_ROOT/lib/lua/LUA_VDIR
>
> Signed-off-by: Haseeb Ashraf <Haseeb_Ashraf@mentor.com>
> ---
>  meta-oe/recipes-devtools/lua/lua_5.3.4.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta-oe/recipes-devtools/lua/lua_5.3.4.bb b/meta-oe/recipes-devtools/lua/lua_5.3.4.bb
> index 8f4e8fe68..1f077e501 100644
> --- a/meta-oe/recipes-devtools/lua/lua_5.3.4.bb
> +++ b/meta-oe/recipes-devtools/lua/lua_5.3.4.bb
> @@ -28,6 +28,7 @@ EXTRA_OEMAKE = "'CC=${CC} -fPIC' 'MYCFLAGS=${CFLAGS} -DLUA_USE_LINUX -fPIC' MYLD
>
>  do_configure_prepend() {
>      sed -i -e s:/usr/local:${prefix}:g src/luaconf.h
> +    sed -i -e s:lib/lua/:${baselib}/lua/:g src/luaconf.h
>  }
>
>  do_compile () {
> --
> 2.17.1
>
> 

      parent reply	other threads:[~2020-04-16 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 10:29 [meta-oe][PATCH 1/2] modify LUA_CPATH_DEFAULT for 64-bit architectures haseeb_ashraf
2020-04-16 10:29 ` [meta-oe][PATCH 2/2] luaposix: add 33.4.0 version recipe which is compatible with lua5.3 Haseeb Ashraf
2020-04-16 18:35   ` [oe] " Khem Raj
2020-04-16 15:50 ` Khem Raj [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=CAMKF1soS6_L4HpzA5WKuJGZLrnqvnq4qcq-zigYfBX0zhS6EpA@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=haseeb_ashraf@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 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.