From: "Denys Dmytriyenko" <denys@ti.com>
To: Alessio Igor Bogani <alessio.bogani@elettra.eu>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] [PATCH] pru-icss: Replace hardcoded lib with libdir variable
Date: Fri, 14 Aug 2020 18:28:04 -0400 [thread overview]
Message-ID: <20200814222804.GO13081@beryl> (raw)
In-Reply-To: <CAPk1OjEtwvkMrGOFUHRGQgQoZ+HEN59cqtmnf=hrkc60kyP-GA@mail.gmail.com>
On Thu, Jul 23, 2020 at 08:49:14AM +0200, Alessio Igor Bogani wrote:
> Hi Denys,
>
> On Wed, 22 Jul 2020 at 23:24, Denys Dmytriyenko <denys@ti.com> wrote:
> >
> > On Sat, Jul 18, 2020 at 09:58:05AM +0200, Alessio Igor Bogani wrote:
> > > Hi Denys,
> > >
> > > Thank you for reply.
> > >
> > > On Fri, 17 Jul 2020 at 22:32, Denys Dmytriyenko <denys@ti.com> wrote:
> > > > NAK, libdir is usually /usr/lib
> > >
> > > Sorry it was my mistake. Are you willing to accept a patch with
> > > ${base_libdir} instead?
> >
> > Any specific reason for this change?
> > I'm not against it, but I haven't seen any setups where ${base_libdir} != /lib
>
> Using usrmerge DISTRO_FEATURE /lib become a symlink against /usr/lib.
Alessio,
Is this still required?
Were you going to submit a new patch with ${base_libdir}?
Please let me know. Thanks.
--
Denys
next prev parent reply other threads:[~2020-08-14 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 9:08 [PATCH] pru-icss: Replace hardcoded lib with libdir variable Alessio Igor Bogani
2020-07-17 20:32 ` [meta-ti] " Denys Dmytriyenko
2020-07-18 7:58 ` Alessio Igor Bogani
2020-07-22 21:24 ` Denys Dmytriyenko
2020-07-23 6:49 ` Alessio Igor Bogani
2020-08-14 22:28 ` Denys Dmytriyenko [this message]
2020-08-15 12:21 ` [PATCH] Replace hard-coded lib with base_libdir variable Alessio Igor Bogani
2020-08-18 21:22 ` [meta-ti] " Denys Dmytriyenko
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=20200814222804.GO13081@beryl \
--to=denys@ti.com \
--cc=alessio.bogani@elettra.eu \
--cc=meta-ti@lists.yoctoproject.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.