All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 1/3] gawk: upgrade from 4.0.2 to 4.1.1
Date: Fri, 6 Jun 2014 10:07:51 +0800	[thread overview]
Message-ID: <53912277.4080107@windriver.com> (raw)
In-Reply-To: <CAJTo0LbN9V7f29md9LNEA5aG9NaLHG6ZiKt8m_72wO=E9hkWpw@mail.gmail.com>

On 06/05/2014 05:42 PM, Burton, Ross wrote:
> On 5 June 2014 06:29, Chen Qi <Qi.Chen@windriver.com> wrote:
>> +FILES_gawk-common += "${datadir}/awk/* ${libexecdir}/awk/* ${libexecdir}/*.so"
> Gawk doesn't install extensions into libexecdir, but $libdir/gawk:
>
> AC_SUBST([pkgextensiondir], ['${pkglibdir}'])
>
> They may end up in the same location but that can't be guaranteed for
> all time (especially when I have a series that changes libexecdir).
>
> Ross
>
>

Hi Ross,

I checked out your branch and saw your changes.

-export libexecdir = "${libdir}/${BPN}"
+export libexecdir = "${exec_prefix}/libexec"

I'll update my patch and send out a V3.
I think this time, I'll also have to modify the gawk recipe of the old 
3.1.5 version.

(P.S. I grepped in the project, and it seems that there are also other 
recipes that may need some changes about the libexec.)

Best Regards,
Chen Qi


  reply	other threads:[~2014-06-06  2:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05  5:29 [PATCH V2 0/3] Package Upgrades Chen Qi
2014-06-05  5:29 ` [PATCH V2 1/3] gawk: upgrade from 4.0.2 to 4.1.1 Chen Qi
2014-06-05  9:42   ` Burton, Ross
2014-06-06  2:07     ` ChenQi [this message]
2014-06-05  5:29 ` [PATCH V2 2/3] grep: upgrade 2.18 to 2.19 Chen Qi
2014-06-05  5:29 ` [PATCH V2 3/3] shadow: upgrade from 4.1.4.3 to 4.2.1 Chen Qi

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=53912277.4080107@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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.
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.