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 44D56A0093 for ; Thu, 10 Mar 2022 23:59:22 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 137C54113F; Thu, 10 Mar 2022 23:59:22 +0100 (CET) Received: from mail-ej1-f53.google.com (mail-ej1-f53.google.com [209.85.218.53]) by mails.dpdk.org (Postfix) with ESMTP id ABA604113E for ; Thu, 10 Mar 2022 23:59:20 +0100 (CET) Received: by mail-ej1-f53.google.com with SMTP id r13so15398210ejd.5 for ; Thu, 10 Mar 2022 14:59:20 -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=tTAQvHAvz3bnqpAfC5Kh4DK5YAD/4Qv7l+SxXnedd10=; b=vw+L52n88zNcUUA+a1ctKh8+4fz+z3m9yHc87IJfE00eECxtEDbm+ycWjZ57Q6VY1R 3vmAZQVGDY8lwV9JT4vBRDWDicWg/3oMYkcSOAA9idn2rYKvccC0L/senWBT/tRmiFB3 2TRBZ0jN1+YX24tk8CNjdnKhFf7HRlTukh9YSQHAxO5R3mxlJ982cct66QQN4EGhA1IJ UOamD0EpSe9cl12fGLN1AloURmIu6hYoW9KdbvlIUDiNRDQAwAPSGH/KqB5XJB7wnWNd uZ7fRLQNzQ++1fpWJaDxD7XSznZ1ukSqkdQJTDkpbQGj/iijecc438+aWOZxDz9FQqUZ K7Xw== X-Gm-Message-State: AOAM532hj48zMzaWCWP1/0ABoHfuQqYe2PA5LDhOWdhkMLj8pmmpq5e0 vgMxuG+FUQ3VUF+ba1ZlhQkMVJgzo2vkQHms9go6S4aWMk0= X-Google-Smtp-Source: ABdhPJxiHnfSRxbpDqjagwwKsDNZxSVE2dg15I/MPOCYX5FnfKbNyfayOBbClolJcx4YNfz/VF8sU0JVFIv0IAUI6lU= X-Received: by 2002:a17:907:2d29:b0:6db:2b1f:333a with SMTP id gs41-20020a1709072d2900b006db2b1f333amr6260861ejc.704.1646953160433; Thu, 10 Mar 2022 14:59:20 -0800 (PST) MIME-Version: 1.0 References: <165CAE28-2A3E-4960-8E57-2EB9A19024DB@akamai.com> In-Reply-To: From: Dan Gora Date: Thu, 10 Mar 2022 19:58:44 -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 7:54 PM Dan Gora wrote: > > 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". Sorry, those are the getentropy() fixes. This is the fix to determine RDSEED at runtime: "[PATCH 0/2] eal: choose initial PRNG seed source at runtime" It was acked but I don't think that it was ever merged.