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 3B220459C0 for ; Tue, 17 Sep 2024 22:21:18 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 04E21402BE; Tue, 17 Sep 2024 22:21:18 +0200 (CEST) Received: from mail-ua1-f49.google.com (mail-ua1-f49.google.com [209.85.222.49]) by mails.dpdk.org (Postfix) with ESMTP id 3DB9640280 for ; Tue, 17 Sep 2024 22:21:16 +0200 (CEST) Received: by mail-ua1-f49.google.com with SMTP id a1e0cc1a2514c-84afff519d6so19507241.2 for ; Tue, 17 Sep 2024 13:21:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google-2018; t=1726604475; x=1727209275; darn=dpdk.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=7fIaBVRn3HmCpwOONvMOIbf0ua1joWlUVQQbwOPdxms=; b=V8hbZ6HSd2sH6S2+IrUAHXFNDeaLBV2xkZIvAk2NawY4Fo0mq+IaXuaLOaKrQSLnr6 nIlEnM+e4s3jsnUWkmeK3cTnxAHQHJS1qY7zM5GqQlSa1d63V2W71bQnj0LqGgmNQWaY xMS52Yv6It8R3QDyIoe/FUy31QY5+MBvxkb8ikWrMI1CtqUtr8p4W1nWYn90yef0CsHb JnPq7z8xV4NRWGwVXLWMr+j6/lBb9pbxu+TG6f1Dz8+lWDhN24fWR+xknJnVpkDdrYYx NmS77scL4hTyo62IFYapCWhwfElVf1e02kOAEFgPPB6Rc0suN12ogUZL7P28tHbiEL3K 6E1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726604475; x=1727209275; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7fIaBVRn3HmCpwOONvMOIbf0ua1joWlUVQQbwOPdxms=; b=sefkiUwJS124jAiT/JfM5r8AnRG+qH7tN5rT88yDLxQ8ZFlKKsvG2h9kKF1ViE4WWS SvmaIS8b1mMCuU14dW/tA74uwbsKgCpUvbPPhM7y+b8NeaOFPO7iTuT9Pu562t21hJDJ pzwrbYMLOtT00jDzS+qIqI3TEIcWOmZZg1Uea+qROXoDGDUhu+y36vvYmK738AHaJ1jF 3ScM1IWSs0+mo5s1/jZrgVjJOG5pdNoWIqGWajz44AZRHKic8sqCzO9gCVGJSNVW0BEA bsWFuQHIP2J/W4lkQH1MrS+TfO97Nk9ohvybnN1UBEnuHvKtlyl9nYil3qzdx5eCiiuB gdzw== X-Gm-Message-State: AOJu0YyCvutEiagpyA/mlSRrmgSWj07ItbldAoaavmiDC88Mj2kTBC7j W6aR98TqtHuW8r5f1ryAdR/FlWh62Y8IixKn0AJMP5hp6qesOpUKKSdhUgFbaTDixBOX6+Z7Fyt ej9hERVw7s3v5augIg0/v2MWo+nXjyxOU7TjSHFGJ9tzppzPE X-Google-Smtp-Source: AGHT+IG/Q/iX7V1+t6TUXsqQTev+jtS0GsxWpKOFxUl00O/z0ttzlllkPwcBQJNisEzRAe2pxVmuVkwXVnPGlQgaIOQ= X-Received: by 2002:a05:6102:26c6:b0:497:7d6b:7f70 with SMTP id ada2fe7eead31-49d4147ebb6mr6842649137.1.1726604475267; Tue, 17 Sep 2024 13:21:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aldrin Date: Tue, 17 Sep 2024 13:21:04 -0700 Message-ID: Subject: Re: Struggling with meson in dpdk 21.11 To: users@dpdk.org Content-Type: multipart/alternative; boundary="0000000000006a9d8e0622566edb" 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 --0000000000006a9d8e0622566edb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Actually, I misunderstood destdir and some of the other context, my apologies. I do think that it makes more sense to use "x86_64-native-linux-gcc" as a prefix and "/opt/intel/dpdk-stable-21.11.7" as a destdir, but that seems unlikely to solve the problem. maybe you can redirect the output of compilation to a log file and share its output? On Tue, Sep 17, 2024 at 12:40=E2=80=AFPM Aldrin wrote: > > > $ cd /opt/intel/dpdk-stable-21.11.7 > > > $ sudo meson -Dexamples=3Dall -Dprefix=3D"/" > > > > -Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta,net/mvpp2,net/nfb,= net/mlx4,net/mlx5,\ > > > > crypto/qat,crypto/aesni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,crypt= o/kasumi,crypto/mvsam,crypto/openssl,\ > > > > crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,net/= szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,\ > > > crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda > build > > > $ cd build > > > $ sudo ninja > > > Don't build as root. Use: > > $ ninja -C build > > I'm not sure this will address the issue, but you should avoid doing most > of these things as root. > > `export INSTALL_PREFIX=3D"/x86_64-native-linux-gcc"` > `meson setup build` > `meson configure -Dexamples=3Dall \ > -Dprefix=3D"${INSTALL_PREFIX}" \ > -Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta, > net/mvpp2,net/nfb,net/mlx4,net/mlx5,crypto/qat,crypto/aesni_gcm,crypto/ae= sni_mb,crypto/armv8,crypto/ccp,crypto/kasumi,crypto/mvsam,crypto/openssl,cr= ypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,net/szed= ata2,raw/ifpga,net/af_xdp,net/ipn3ke,crypto/ipsec_mb,crypto/ipsec_mb,crypto= /mlx5,compress/mlx5,gpu/cuda > \ > build` > `meson compile -C build` > `meson install -C build` > > where I do notice that you're setting some conflicting options is that yo= u > have `-Dprefix=3D"/"` when configuring and you also have > `--destdir=3D../x86_64-native-linux-gcc` when installing. I'm not sure wh= y > you would set these to different paths unless you're essentially on a > root-only system and you are doing everything from the root directory? > > In my example above, I set a variable, INSTALL_PREFIX, and use that in th= e > configure step instead. Then, when you install, just let it install to th= e > prefix that you specified. Presumably, this will ensure that all paths ar= e > correct whereas setting a different destdir from the prefix could > potentially mismatch some paths. > > --0000000000006a9d8e0622566edb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Actually, I misunderstood destdir and some of the oth= er context, my apologies.

I do think that it makes= more sense to use "x86_64-native-linux-gcc" as a prefix and &quo= t;/opt/intel/dpdk-stable-21.11.7" as a destdir, but that seems unlikel= y to solve the problem.

maybe you can redirect the= output of compilation to a log file and share its output?

On Tue= , Sep 17, 2024 at 12:40=E2=80=AFPM Aldrin <akmontan@ucsc.edu> wrote:
> > $ cd /= opt/intel/dpdk-stable-21.11.7
> > $ sudo meson -Dexamples=3Dall -D= prefix=3D"/"
> > -Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta,net/mvpp2,= net/nfb,net/mlx4,net/mlx5,\
>=20 > crypto/qat,crypto/aesni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,cr= ypto/kasumi,crypto/mvsam,crypto/openssl,\
>=20 > crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,n= et/szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,\
>=20 > crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda bui= ld
>=20 > $ cd build
>=20 > $ sudo ninja

>=20 Don't build as root. Use:
>=C2=A0 $ ninja -C build
<= div>

I'm= not sure this will address the issue, but you should avoid doing most of t= hese things as root.

`export INSTALL_PREFIX=3D"/x86_64-native-linux-gcc"`
`meson setup build`=
`meson configure -D= examples=3Dall \
=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 -Dprefix=3D"${INSTALL_PREFIX}"=C2=A0=C2=A0 \=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 -Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta,net/mvpp2,net/nfb,net/mlx4,net/mlx5,crypto/qat,crypto/a= esni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,crypto/kasumi,crypto/mvsam= ,crypto/openssl,crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5= ,net/pcap,net/szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,crypto/ipsec_mb,cryp= to/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda \
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 build`
`meson compile -C build`
`meson install -C build`

= where I do notice that you'= ;re setting some conflicting options is that you have `-Dprefix=3D"/&q= uot;` when configuring and you also have `--destdir=3D../x86_64-native-linu= x-gcc` when installing. I'm not sure why you would set these to differe= nt paths unless you're essentially on a root-only system and you are do= ing everything from the root directory?

In my example above, I set a variable, INSTALL_PREFIX, a= nd use that in the configure step instead. Then, when you install, just let= it install to the prefix that you specified. Presumably, this will ensure = that all paths are correct whereas setting a different destdir from the pre= fix could potentially mismatch some paths.

--0000000000006a9d8e0622566edb--