DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>
Subject: RE: [PATCH] doc/linux_gsg: remove note referring to old pkg-config
Date: Wed, 9 Apr 2025 07:54:18 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9FBA6@smartserver.smartshare.dk> (raw)
In-Reply-To: <20250408171902.2833850-1-bruce.richardson@intel.com>

> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Tuesday, 8 April 2025 19.19
> 
> Latest DPDK releases no longer officially support RHEL 7 as a target
> platform, so remove the note about pkg-config not working on those
> systems.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  doc/guides/linux_gsg/sys_reqs.rst | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/doc/guides/linux_gsg/sys_reqs.rst
> b/doc/guides/linux_gsg/sys_reqs.rst
> index 5a7d9e4a43..4c9d0c55c0 100644
> --- a/doc/guides/linux_gsg/sys_reqs.rst
> +++ b/doc/guides/linux_gsg/sys_reqs.rst
> @@ -35,13 +35,6 @@ Compilation of the DPDK
>      * For Ubuntu/Debian systems these can be installed using ``apt
> install build-essential``
>      * For Alpine Linux, ``apk add alpine-sdk bsd-compat-headers``
> 
> -.. note::
> -
> -   pkg-config 0.27, supplied with RHEL-7,
> -   does not process the Libs.private section correctly,
> -   resulting in statically linked applications not being linked
> properly.
> -   Use an updated version of ``pkg-config`` or ``pkgconf`` instead
> when building applications
> -
>  *   Python 3.6 or later.
> 
>  *   Meson (version 0.57+) and ninja
> --
> 2.45.2

Acked-by: Morten Brørup <mb@smartsharesystems.com>


      reply	other threads:[~2025-04-09  5:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 17:19 Bruce Richardson
2025-04-09  5:54 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35E9FBA6@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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 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).