From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 68043A0093 for ; Thu, 10 Mar 2022 23:55:26 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E76034113F; Thu, 10 Mar 2022 23:55:25 +0100 (CET) Received: from mail-ej1-f44.google.com (mail-ej1-f44.google.com [209.85.218.44]) by mails.dpdk.org (Postfix) with ESMTP id 9BBF64113E for ; Thu, 10 Mar 2022 23:55:24 +0100 (CET) Received: by mail-ej1-f44.google.com with SMTP id p15so15369816ejc.7 for ; Thu, 10 Mar 2022 14:55:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vKpL/x0kmUqMihVtWEN5WBJ29Dx4bDuIFiyWgMtR58w=; b=NMzrD4KtUksN6ri6lWLJuX7SrNPG/rYpRTFSmlbECcIaY4pYwveUEulEPxmrV3C5Ew o7NZMgv9P0MIAb33khXVd7lbF7j7ZuezV6c3lMVmC67n70uJJcX3JI4Vs0MDMjBkQ6Qe d7eOuzCEAhkCGYYikNyQ0rnBj0kuTPo2zKBXvYGPz0bULrWcBsZgVNQc8HgI30uwetMO GCHrN+Q+DTosh+J+EfAyUB0NncY5+80lF59svBylGwVo/E/EhXh+RvgOu8e5ugB2HPy+ eLZXk9MeXYlDu/tmW9TJIeOJ/NhDDhdgxxXSQI2EmQYKhafkt7w97i1c8XEZ9gwQiebv vj1g== X-Gm-Message-State: AOAM531aPFA4Dbb2V2rv1FVk0Sjuv+tSAAs3lhdFolH0hIkETFBT3zHk uBdQ90exrfqRIf1uaMLwf8sMii/XZU7lqIKAv66jHHnr X-Google-Smtp-Source: ABdhPJzKEnt/fBMfZnqxrCJ+boXIBGMxv8JceA/GDPqYAbryNCtPUbqkoSFW2m1bGzxCQIPSBa7w/Cb4SfKKGl3v9Wk= X-Received: by 2002:a17:906:c14c:b0:6d7:1278:d80c with SMTP id dp12-20020a170906c14c00b006d71278d80cmr6384375ejc.660.1646952924300; Thu, 10 Mar 2022 14:55:24 -0800 (PST) MIME-Version: 1.0 References: <165CAE28-2A3E-4960-8E57-2EB9A19024DB@akamai.com> In-Reply-To: <165CAE28-2A3E-4960-8E57-2EB9A19024DB@akamai.com> From: Dan Gora Date: Thu, 10 Mar 2022 19:54:48 -0300 Message-ID: Subject: Re: meson options - build vs target machine cpuflags question To: "Sanford, Robert" Cc: "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Thu, Mar 10, 2022 at 11:46 AM Sanford, Robert wrote: > > Hello All, > > We build a DPDK 21.05 app on Intel x86 machines with RDSEED in cpuflags, and may run it on machines *without* RDSEED. > This results in a fatal error ... > ERROR: This system does not support "RDSEED". > Please check that RTE_MACHINE is set correctly. > EAL: FATAL: unsupported cpu type. > > I try adding -Dplatform=haswell when running meson, (because gcc man page indicates that haswell is last arch w/o RDSEED) but get the same result. > Until we resolve it, our workaround is changing the error-out in rte_cpu_is_supported() to just print a warning and continue. > We don't have direct access to automated build machines, we go through change request processes, and so we can't rapidly try too many things. > > Is there a better meson option, such as machine=haswell, or something else that will work? > > Thanks in advance, > Robert Sanford I tried four times to get a simple fix for this (and the lack of getentropy() on older glibc) to determine the entropy source at run time and got nothing but an endless raft of shit and ridiculous criticisms that I completely gave up trying to contribute to DPDK ever again. The DPDK developers think that it's your responsibility to have a separate build system for each of your target systems and platforms and that if you don't you're basically a big dummy. Don't believe me? Go look through the archives: "[PATCH 2/2] eal: resolve getentropy at run time for random seed" "[PATCH v4 2/2] eal: emulate glibc getentropy for initial random seed". I suggest that you just fork DPDK and use one of those patches and just maintain a separate DPDK tree. That's what I did. It's way easier than trying to get anything upstream. thanks dan