From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id EFE8EA0518 for ; Fri, 24 Jul 2020 14:04:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E7D671C039; Fri, 24 Jul 2020 14:04:31 +0200 (CEST) Received: from mail-wr1-f68.google.com (mail-wr1-f68.google.com [209.85.221.68]) by dpdk.org (Postfix) with ESMTP id 3D7331C039 for ; Fri, 24 Jul 2020 14:04:30 +0200 (CEST) Received: by mail-wr1-f68.google.com with SMTP id f18so8101963wrs.0 for ; Fri, 24 Jul 2020 05:04:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=j/9VEf21lLQKfo2DcObbl/4lIYB8nIdFmRzWinAOCFw=; b=B6k3AlUL/ZT6z+7JBRxJqecgKkYYQ4fZtDayoZdd/wUZS+aP+pAK3yCvIFBz9kvEeG +96AzXhlV0p2b1TzJ6XAokaT4gEy0WpEUBXFz2Ixax45jn8G5B0SOs2N7dWBxaY7/y9f tEGkPWcvdDMCp05/jLPn1nrN/mg256QJVttIZkGXtDyjHAqeR2u12WvIzaKgU5Aohd0v hqZUc8SocNxPV5DKnBVMZsL5ErdkeRfdFbthbJjWbQDxKbo2dSbDX4My98EYi/gg+3iw oy84KAdQXRXlqPC/jMy9MftK7m8qjrJFyWUmZAK+EgnJL7Ktmaj+G4dkmhE1D9voJUJN 4eBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=j/9VEf21lLQKfo2DcObbl/4lIYB8nIdFmRzWinAOCFw=; b=BBBNddovVQlZ8lubYwOi5v8uyfj1gmQrMLd+XATi8HWPU1E7yCNQmfPCe20UK/mZ8a NgNQZLvZ2YqrjXuqg0AetrWp4LT56qjm+H9AMqKdf1F7P4FGtmhG4+lSuDBoHwlkp9HT YEQTNa6OK5VzpD63G8JF4H5PzdE7UTbBn+Xw98rqzIV772S0z9Dqz/HBgC1Bzh/vN82/ TCP2XCxgSRpmxrOLWKN5W1WddkSNt9FcoQoBbXoyc3AyoMD2Mctc/g5MTBL0Ui8jBZoU 0vfs5W2FfprYC34/ns3+0dJAJ1uIw642NE5gfsZQV1DBw5kpsFUcCVd7r6AJnq/D1JjV tYyg== X-Gm-Message-State: AOAM532IgRNRA7lnQ1YgwSY5olqRvlqgGmUKmR1047dobPMjBbxmvbDW /4v1WOaYX11yAYAxdMLnw7g= X-Google-Smtp-Source: ABdhPJx8BoYFJZbq40XO6+fYw7P8JHQ856hbNgcyRByKRfr1Xs8mdutEjIOmI6lE3Uf5e/YMN63VEA== X-Received: by 2002:a5d:5151:: with SMTP id u17mr8459023wrt.154.1595592269958; Fri, 24 Jul 2020 05:04:29 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id g18sm1253043wru.27.2020.07.24.05.04.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Jul 2020 05:04:24 -0700 (PDT) From: luca.boccassi@gmail.com To: Thomas Monjalon Cc: Bruce Richardson , David Marchand , dpdk stable Date: Fri, 24 Jul 2020 12:58:14 +0100 Message-Id: <20200724120030.1863487-56-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200724120030.1863487-1-luca.boccassi@gmail.com> References: <20200724120030.1863487-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: update build instructions in the Linux guide' has been queued to stable release 19.11.4 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to stable release 19.11.4 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 07/26/20. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Luca Boccassi --- >From 15318529bd10ad8cc0c90aa152b369c23853d580 Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Wed, 17 Jun 2020 23:41:25 +0200 Subject: [PATCH] doc: update build instructions in the Linux guide [ upstream commit 520bbb9cd9215c7139244b06f5041722e91bf14a ] Before removing the "make" build system completely, the Linux guide instructions are made more concise and accurate. Some detailed explanations are also available in doc/guides/prog_guide/dev_kit_root_make_help.rst This is the swan song for makefile system, in order to have accurate information backported in LTS. Signed-off-by: Thomas Monjalon Acked-by: Bruce Richardson Acked-by: David Marchand --- doc/guides/linux_gsg/build_dpdk.rst | 66 ++++++++--------------------- 1 file changed, 18 insertions(+), 48 deletions(-) diff --git a/doc/guides/linux_gsg/build_dpdk.rst b/doc/guides/linux_gsg/build_dpdk.rst index 4aeb4697d..c536e354e 100644 --- a/doc/guides/linux_gsg/build_dpdk.rst +++ b/doc/guides/linux_gsg/build_dpdk.rst @@ -167,60 +167,32 @@ Installation of DPDK Target Environment using Make is therefore recommended that DPDK installation is done using meson and ninja as described above. -The format of a DPDK target is:: +Get a native target environment automatically:: - ARCH-MACHINE-EXECENV-TOOLCHAIN - -where: - -* ``ARCH`` can be: ``i686``, ``x86_64``, ``ppc_64``, ``arm64`` - -* ``MACHINE`` can be: ``native``, ``power8``, ``armv8a`` - -* ``EXECENV`` can be: ``linux``, ``freebsd`` - -* ``TOOLCHAIN`` can be: ``gcc``, ``icc`` - -The targets to be installed depend on the 32-bit and/or 64-bit packages and compilers installed on the host. -Available targets can be found in the DPDK/config directory. -The defconfig\_ prefix should not be used. + make defconfig O=mybuild .. note:: - Configuration files are provided with the ``RTE_MACHINE`` optimization level set. Within the configuration files, the ``RTE_MACHINE`` configuration value is set to native, which means that the compiled software is tuned for the platform on which it is built. - For more information on this setting, and its possible values, see the *DPDK Programmers Guide*. -When using the IntelĀ® C++ Compiler (icc), one of the following commands should be invoked for 64-bit or 32-bit use respectively. -Notice that the shell scripts update the ``$PATH`` variable and therefore should not be performed in the same session. -Also, verify the compiler's installation directory since the path may be different: +Or get a specific target environment:: -.. code-block:: console + make config T=x86_64-native-linux-gcc O=mybuild - source /opt/intel/bin/iccvars.sh intel64 - source /opt/intel/bin/iccvars.sh ia32 +The format of a DPDK target is "ARCH-MACHINE-EXECENV-TOOLCHAIN". +Available targets can be found with:: -To install and make targets, use the ``make install T=`` command in the top-level DPDK directory. + make help -For example, to compile a 64-bit target using icc, run: +Customize the target configuration in the generated ``.config`` file. +Example for enabling the pcap PMD:: -.. code-block:: console + sed -ri 's,(PMD_PCAP=).*,\1y,' mybuild/.config - make install T=x86_64-native-linux-icc +Compile the target:: -To compile a 32-bit build using gcc, the make command should be: - -.. code-block:: console - - make install T=i686-native-linux-gcc - -To prepare a target without building it, for example, if the configuration changes need to be made before compilation, -use the ``make config T=`` command: - -.. code-block:: console - - make config T=x86_64-native-linux-gcc + make -j4 O=mybuild .. warning:: @@ -229,15 +201,13 @@ use the ``make config T=`` command: If the DPDK is not being built on the target machine, the ``RTE_KERNELDIR`` environment variable should be used to point the compilation at a copy of the kernel version to be used on the target machine. -Once the target environment is created, the user may move to the target environment directory and continue to make code changes and re-compile. -The user may also make modifications to the compile-time DPDK configuration by editing the .config file in the build directory. -(This is a build-local copy of the defconfig file from the top- level config directory). +Install the target in a separate directory:: -.. code-block:: console + make install O=mybuild DESTDIR=myinstall prefix= - cd x86_64-native-linux-gcc - vi .config - make +The environment is ready to build a DPDK application:: + + RTE_SDK=$(pwd)/myinstall/share/dpdk RTE_TARGET=x86_64-native-linux-gcc make -C myapp In addition, the make clean command can be used to remove any existing compiled files for a subsequent full, clean rebuild of the code. @@ -245,5 +215,5 @@ Browsing the Installed DPDK Environment Target ---------------------------------------------- Once a target is created it contains all libraries, including poll-mode drivers, and header files for the DPDK environment that are required to build customer applications. -In addition, the test and testpmd applications are built under the build/app directory, which may be used for testing. +In addition, the test applications are built under the app directory, which may be used for testing. A kmod directory is also present that contains kernel modules which may be loaded if needed. -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2020-07-24 12:53:50.762877735 +0100 +++ 0056-doc-update-build-instructions-in-the-Linux-guide.patch 2020-07-24 12:53:48.275006236 +0100 @@ -1,8 +1,10 @@ -From 520bbb9cd9215c7139244b06f5041722e91bf14a Mon Sep 17 00:00:00 2001 +From 15318529bd10ad8cc0c90aa152b369c23853d580 Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Wed, 17 Jun 2020 23:41:25 +0200 Subject: [PATCH] doc: update build instructions in the Linux guide +[ upstream commit 520bbb9cd9215c7139244b06f5041722e91bf14a ] + Before removing the "make" build system completely, the Linux guide instructions are made more concise and accurate. Some detailed explanations are also available in @@ -11,8 +13,6 @@ This is the swan song for makefile system, in order to have accurate information backported in LTS. -Cc: stable@dpdk.org - Signed-off-by: Thomas Monjalon Acked-by: Bruce Richardson Acked-by: David Marchand