From: Bruce Richardson <bruce.richardson@intel.com>
To: Gagandeep Singh <g.singh@nxp.com>
Cc: <dev@dpdk.org>
Subject: Re: [v1 3/3] meson: skip symlinks to PMDs script on no sub directory
Date: Tue, 6 Aug 2024 14:57:24 +0100 [thread overview]
Message-ID: <ZrIrxAKVkn-wDTJf@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20240806134218.3619913-4-g.singh@nxp.com>
On Tue, Aug 06, 2024 at 07:12:18PM +0530, Gagandeep Singh wrote:
> if user gives option -Ddrivers_install_subdir= or
> -Ddrivers_install_subdir=. to install all the PMDs in
> parent directory, The post installation script
> "symlink-drivers-solibs.sh" can create invalid library file
> named 'librte_*.so*' or meson installation errors:
>
> ln: './librte_*' and './librte_*' are the same file
> FAILED: install script '/bin/sh /home/nxa12342/upstream/dpdk/config/.
> /buildtools/symlink-drivers-solibs.sh lib/x86_64-linux-gnu .' exit code 1,
> stopped
> FAILED: meson-install
>
> This patch removes this post-install script execution to symlink
> the PMDs libraries when no sub directory is given.
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
prev parent reply other threads:[~2024-08-06 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 13:42 [v1 0/3] meson options related changes Gagandeep Singh
2024-08-06 13:42 ` [v1 1/3] meson: add a meson option to install examples Gagandeep Singh
2024-08-06 13:58 ` Bruce Richardson
2024-08-07 4:09 ` Gagandeep Singh
2024-10-17 15:46 ` Thomas Monjalon
2024-08-06 13:42 ` [v1 2/3] meson: add a meson option to install examples source Gagandeep Singh
2024-08-06 14:01 ` Bruce Richardson
2024-08-07 4:08 ` Gagandeep Singh
2024-10-17 15:50 ` Thomas Monjalon
2024-08-06 13:42 ` [v1 3/3] meson: skip symlinks to PMDs script on no sub directory Gagandeep Singh
2024-08-06 13:57 ` Bruce Richardson [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=ZrIrxAKVkn-wDTJf@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).